What could be the underlying reason behind allowing lookup only through list formatted line items, not through a normal text formatted line item?
The data is stored/calculated at the intersection of the different dimensions (Lists, Time, Versions)
Text values are not part of the list definition (Name and Code) are, so that is why we use formatted line items, and use FINDITEM to return the list member for use in modelling
It is not the same structures as Excel, which uses generic rows and columns. Anaplan is much more structured than that
It would be easier not to have to use FINDITEM to match/transform, but that is a whole different topic!!
I hope that explains it
David
Hi,
I assume it's a matter of performance. I can't imagine how lookup function could work without a list. Even if there will be x records for a single line item text formated, there have to be created a kind of temporary list.
Regards
Tomasz
@T_Caban
It's not really a performance issue (although it probably would be!), it is just not the way Anaplan works.
Everything has to be linked back to a specific object. Text is a free form data point, so can't be used to tie into structures
Test - Please Ignore
Hello folks, Does anyone know how to work around the Polaris limitation of using the Formula or Ratio summary method alongside the Closing Balance within the same line item? I have a Business Unit list where the total (All BUs) must display the Corporate (1 of 20 leaf items under All BUs total) number of Unique Customers.…
Has anyone found success using Anaplan XL with Polaris models in a shared drive with or without concurrent users? My team has experienced a variety of errors, login failures, etc. sometimes it works, sometimes it doesn't. We've been recommended to save and edit files locally, which helps but certainly with its limitations…
