I'm trying to export data from my Anaplan view(s) in a way that it basically represents a "fact table" (dimensions and line items as columns, and the corresponding values as rows) for easy processing.
GRID_CURRENT_PAGE/GRID_ALL_PAGES seems out of the question since the exported data is the same as in the UI and needs way too many transformations.
TABULAR_SINGLE_COLUMN is a lot more promising but the only problem is that all line items are a single column in itself and values are another column. So basically, I have Units Sold for X person in row 2 and then the 2nd line item almost 500+ rows after for the same dimensions.
If I added another line item here, I imagine it would be another 1000+ rows further down. This severely tanks performance if I want to change the Line Items into columns with their corresponding values.
Above output would be perfect if the API separated the line items as well as their own columns.
Then, I'm testing TABULAR_MULTI_COLUMN. I'm not exactly sure what the principal or use case behind this is. If I pivot my data like this:
And export as multi column, I basically get some kind of single column + grid CSV mix, with multiple header rows:
If I leave nothing in columns:
I get a CSV without headers somehow resembling TABULAR SINGLE COLUMN:
The only way to get the representation I want is if I move "Line Items" to columns and everything else out:
This is basically perfect.
Is there any API or easy way to basically get TABULAR SINGLE COLUMN + LINE ITEM COLUMN always without changing/creating other views? Or some way to ask the API get this data with X,Y,Z dimension in rows/pages/columns?
I'm also confused on what TABULAR MULTI COLUMN is actually doing? I get the GRID and SINGLE flattening, but what's the principal behind this? Any clarification on this would also be helpful.
