Allow for line item subset to be more than just number formatted

Allow for line item subset to be more than just number formatted


Description of the enhancement required:

Line Item Subsets are often used to build filter modules, as an alternative to using the Show/Hide functionality. Using a Boolean against a Line Item Subset on a filter module makes it very easy to select which columns should be shown or hidden on a dashboard.


An example of the enhancement:
It would be great if you could add Line Items of all formats (not just number) to a Line Item Subset for this purpose. Perhaps you could utilize the Line Item Subset type field to setup certain Line Item Subsets to allow both number/non-number formats.

Community Manager
Status changed to: Considered for Future Roadmap
Occasional Contributor

The restriction that the format is the same across all line items in a line item subset should apply only if a COLLECT() formula is used.

Certified Master Anaplanner


I totally understand the constraints of COLLECT() function.

But why COLLECT() should work only on NUMERIC linet items ? Why do not apply the summary property of non-numeric Line items ( ANY for boolean, FIRSTNONBLANK for boolean. texts , etc..)


In the below discussion there is also other reason that line-items subsets could be used also for non-numeric line items: create a dynamic filter to show-hide line-items in dashboard:





Occasional Contributor

Hi Alex,

COLLECT() could work on any line item subset where all line items in the subset are of the same semantic* type. The summary type of the source line item would be used where applicable.

* Semantic type adds more detail to the datatype where applicable, i.e. which list, or which period granularity.
e.g. a line item formatted as list A has datatype 'List', and semantic type 'List: A'.


Certified Master Anaplanner

Thanks Dan for explanation. 


However, my first goal into accepting in line items subset the non-numerical formatted line-items was to be able to create a system to dynamically show-hide columns  in a dashboard, similar with grouping columns from Excel and not to be able to use the COLLECT() function. 🙂


Now this can be done only for numeric line-items creating a separate module with the subset and boolean line-items, but I think it would be really cool to have it also for non-numeric line-items


For me it would be acceptable that for non-numeric line-items selected in a subset, if used in a module with COLLECT() function, to receive the result 0 or null or 'NaN'.


What do you think ?







Community Boss

We could use this in cases where COLLECT() is not used

  • Version Formulae
  • DCA on line items (commonly requested since DCA was launched)
  • Used for mapping with LOOKUP and SUM to map between lists members and line items


Certified Master Anaplanner

DavidSmith I know that now you are a part of Core team, so I hope the development will be speed up multiply times..


This feature is "Must have" one. 

Collect() function shouldn't disable the functionality of whole model.

There are a lot of situations when LIS is used without Collect() 

For example it's neccesary for dashboard design.


Last status change was  ‎07-18-2018 12:26 PM to: Concidered for future roadmap. It was practicaly year and a half ago.

Whas is actual status for this idea?


Frequent Contributor

Bump for any update on the status of this idea.


Line Item Subsets are so versatile, but are severely hamstrung by only being able to include numeric line items.

Community Boss


I am looking at the big list of requests, so I'll definitely add it into the mix


Certified Master Anaplanner

Any update about this?  It would be really useful to make showing/hiding columns dynamically in a page valid not only for numerical table grids...


Agree with @alexpavel  - any update?

Certified Master Anaplanner

Indeed would be extremely interested in any update regarding the possibility of getting this feature. 


Maybe @rob_marshall, would have any insights for the curious bunch here? 






I wish I had an update, but sadly I do not.

Certified Master Anaplanner

Any update on this? 

It's really a pity not having the possibility to create dynamic filters for non-numeric line-items. 


I think it would be acceptable that, if a line-item subset would contain also non-numeric line-items the COLLECT() will return an error. COLLECT() to be used exclusively only if ALL line-items from the line-item subset are numeric. 


Another use case:  Having a combination list + Month. There are non-numeric line-items in the module which define the properties of the combi list and numeric line-items to input data. 


It is impossible to create a dynamic layout where you need to show in columns the properties and the 12 months. This unbalanced layout structure cannot be create in NUX and in a Saved View (in classic) you can do it manually and hard-coded.  (see below picture). 


Having the possibility to create filters on non-numeric line-items would solve this issue. 





It would be really nice to solve this as soon as possible. 



New Contributor

I strongly support Alex' opinion in this regard. Especially in the new UX we absolutely need a solution for dynamic filtering of non-numeric line items. The easiest way would be with line item subsets for those line items. If this is not an option (and it looks like it as this idea exists for more than 3 years and was not delivered) is there any practical workaround?

Certified Master Anaplanner

I will throw some more support on this request - allowing Line Item Subsets to include more than just numerica data would greatly increase their functionality. I am very surprised that there has not been any update on this, despite the great number of comments and support here. It is a feature request that continues to be relevant, and could be combined with the newest User Experience features to make for some amazing and intuitive presentation of information. 


Ideally the COLLECT function could be used to aggregate multiple data types (throwing an error if there were different data types in the LIS, and requiring an aggregation method to be specified for non-numeric formats), but even if COLLECT could only be used on number format data it would still be a great win.