Increase limit of row field when pivoting


It would be really helpful for myself and colleagues if more than just three items could be dragged into the row field whilst pivoting a module.


This would also be really helpful for zero suppression on Anaplan exports as well as saving the need to manipulate Anaplan exports in Power Query (or similar data transformation tool) to produce only one amount/values column.

22 votes

New · Last Updated


  • Status changed to: New
  • This may be an oversimplistic answer, apologies if this is the case, but have you looked at saving your exports as tabular multiple column? If you choose the option to omit zeros or filter based on a boolean you will create a more efficient data set in your export options, which of course can be saved and repeated based on the view you are exporting.


    There is also the potential for pivoting and selecting to have restricted list member(s) selected - generally I see these as standard dimensions (versions, time, etc) - show up in pages? I have done this a couple of times before to solve for creating saved views that have multiple nested requirements. You should also be able to reselect levels to the leaf level in order to help with performance on those saved views should you need. In addition, if you have performance issues on a saved view, you can create a boolean line item to filter on so that you aren't testing for 0 within the filter function, but in the module itself.



  • Thanks for this idea..


    I am not sure why the "Tabular multiple column" option is available only on export actions... this practically put in "rows area" ALL the lists of the module, except of the line items (which are in columns). 

    If you have this possibility on export actions, why not also for a saved view... :).


    the "Tabular multiple columns" or "Tabular single columns" options always export ALL the line-items... which sometimes is not what the users would like.


    It would be really helpful to have this option to put more than 3 lists in "rows area" and avoid the creation of intermediary combined lists.


    It would be also helpful to have the "Omit/Suppress empty rows" option also for saved views and not only for export actions.

    It seems that this option is much more faster than applying the filter on a saved view.





  • Even tabular format is existing on export, it won't work in all scenarios as many data exchange have to be on 'flat file' format. Therefore, multiple column headers are a must have feature.


    Do please let me know if you any other suggestions.

Get Started with Idea Exchange

See our Submission Guidelines and Idea Evaluation Criteria, then start posting your own ideas and showing support for others!