Hi All, Thanks for your help on this! I've come up with a solution to the problem. As I want to have one master list in a data hub model that pushes out to other models I need to be able to preserve the unique ID of the data hub list so that if any list items are edited (e.g. display name changes), any associated data remains. This will also preserve the ability to add/remove list items. In my master model I created a module with my numbered list with a line item called "UID", text formatted. I concatenated "UID" with the NAME function to get the Anaplan numbered list name (i.e. the #1, #2, #3 name not the display name). The end formula looked like this: "UID" & NAME(ITEM('Organisation L3')). In my child model I then created a numbered list and set up my import, for the numbered list, by connecting to another Anaplan model, the data hub model in this case. I connected to the module previously created (not the list). I removed the source from the Name property field and mapped my UID line item to the code property field. I then set the import to be unique by code only and ran the import. I found that if I did not concatenate "UID" to the default Anaplan numbered list names the import would fail - presumably "#" & NUMBER formats are reserved for the system. This method aligns the numbered lists in my data hub model to the lists in my child models, a 1 to 1 relationship that won't change if the list item is edited AND will enable me to add and remove items in numbered lists within my data hub model and push any hierarchy updates to other models. The key benefit to this is that I can have one hierarchy stored in one model. This will be especially useful for my use case as I have a number of models which all use the same hierarchy.
... View more
