When not to use Numbered Lists?

michael.jones

Given how flexible numbered lists are, is there a reason why I should not make all lists in a model 'numbered'?

Accepted answers

JaredDolich

@michael.jones

Two reasons that come to my mind immediately:

Numbered lists essentially reduce you to one primary key, the code. This can also present some challenges when moving system module properties of that list from one model to another because you have to reference the code. If the code is a made up value for the purposes of Anaplan then it really is not meaningful. It also then requires you to identify the system generated ID from Anaplan if the code value needs to change and is synchronized with another model. Good example would be Data Hub to Spoke application. If the code changes, how else would you know how to find the list value that changed so you can edit the code? Otherwise, you'll just be adding another list item.
If you need the ability to create list items from a dashboard you no longer need to use a numbered list. You can create forms in the new UX.

I remember reading a good debate between @rob_marshall @DavidSmith and @Misbah whether numbered lists are even needed. I'll see if I can find it. They may have some additional input for you.

DavidSmith

@michael.jones

I actually look at it the other way - Why would I use a number list? - In most of my Anaplan modelling I use normal lists. Even for "combination" lists as generally you are in control of the code and name, and the complexity around moving data between modules/models is a problem, as @JaredDolich outlined

So I only use Number lists when I need to take advantage of the specific features (display names, assign, copy, delete branch etc.)

Going forward, I'd prefer that we unify lists and only have 1 type, so taking the best bits of functionality from both

David

All comments

JaredDolich

@michael.jones

Two reasons that come to my mind immediately:

Numbered lists essentially reduce you to one primary key, the code. This can also present some challenges when moving system module properties of that list from one model to another because you have to reference the code. If the code is a made up value for the purposes of Anaplan then it really is not meaningful. It also then requires you to identify the system generated ID from Anaplan if the code value needs to change and is synchronized with another model. Good example would be Data Hub to Spoke application. If the code changes, how else would you know how to find the list value that changed so you can edit the code? Otherwise, you'll just be adding another list item.
If you need the ability to create list items from a dashboard you no longer need to use a numbered list. You can create forms in the new UX.

I remember reading a good debate between @rob_marshall @DavidSmith and @Misbah whether numbered lists are even needed. I'll see if I can find it. They may have some additional input for you.

DavidSmith

@michael.jones

So I only use Number lists when I need to take advantage of the specific features (display names, assign, copy, delete branch etc.)

Going forward, I'd prefer that we unify lists and only have 1 type, so taking the best bits of functionality from both

David

Misbah

@michael.jones

Yes, many reasons not to make your list numbered list (let's not talk about all). If you have duplicate names but unique codes in your list, that should be the right call for you to make it a numbered list.

All those 4 actions that @DavidSmith mentioned, you will have to use Numbered lists. I personally am not a huge fan of numbered list, to me general lists are more flexible.

Misbah

swatikhedkar

I have a level 2 P&L list... see it as a sub group under main p&L list. the inputs happen at P&l level 2 list. this list is created from actuals that come in. We made this list as normal list because of the nature of this list as we didnt wanted a P&l level 2 item with different code and same name to be created. we recently got such case and a warning was thrown. what is ur take on this? should list like P&L sub group made numbered list ? One more issue i see it in making numbered list is then the user will not be able to identify which item it was with same name as we dont display code on DB and difficult to remember code and search .

Quick Links

Can you help?

Unanswered questions

Azure SQL Connection, database name with Hyphens in Data Orchestrator
I am attempting to connect to an azure SQL database vis at the MSSQL connector in data orchestrator but am having issues and I believe it is due to hyphens in database name (which is a fairly standard naming convention I will note!) Example below (fake credentials) - has anyone else encountered similar and is there a way…
12.4.1 Activity: Create Saved View for Non Employee Expenses
Hi, for some reason my shipping costs are the same over every month and I don't know what to do to fix it.
Workaround for Formula & Closing Balance summary methods together in Polaris
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.…