Numbered Lists renumbering

Hi,

The number of IDs on the numbered list is 999,999,999 (based on information in topic related with numbered lists)- what about reaching this limit. Is there any list renumbering possibility?

Accepted answers

DavidSmith

Just to clarify, this restriction applies to all lists, not just numbered lists.

We often see this happening with transactional data loads where the whole list is cleared out each time before being re-loaded and where "combination of properties" are used to create the numbered list. With large datasets, if this is done on a daily basis, the index will reach the limit in a very short time.

It is best practice to try and avoid mass "delete and re-load" for this reason. Techniques include using incremental imports and having a unique key in the data source wherever possible. It is important to try and work with the owners of the source data to aim for correct format in the source data and always use a unique key if possible. Aside from minimising the issue above, an import using a key is much quicker

Very often this mass delete / reload is not actually required. If a unique key is used, if the data changes in the source from the values loaded previously, the new update will update the "record" with the new value

I hope that helps

David

All comments

bdeaton

My understanding is that once the limit is reached the only thing to do is to create a new numbered list and repoint everything to the new list.

I'd love to hear from others if that is not the case, though.

Damian_Broj

Repointing everything related with the list is often enormous workload for the admin. When you handle multiple models having ALM structure and using numbered list as a production list and non production modules uses the production list then repointing can cause more problems and work.

Personally i have a numbered list containing transaction data and incrementing month over month for tousands of new items that sometimes need to be reloaded and then the number counter increments even if "old" transactions are removed.

in the end in the list can be 200,000 items but the # counter can achieve limit- ideal solution would be that removed items makes new "free slots" and new coming items would be numbered starting from the lowest "free slot" available

hope to read some thoughts from other users and especially from Anaplan Support

Damian_Broj

anyone?

greg_reynolds

Hi - this is a fairly common scenario for usages of numbered lists and a number of users have experienced the same frustration that you have. We are looking at an automatic solution for this problem to be released in the near future. In the meantime, if you are stuck then please contact support and they may be able to reset the sequence for you.

Hayk

Hi,

You can mark that list as a "production data" and create model from revision tag (Revision Tags tab). It'll be reset in a new model.

In some cases it is easier than creating new list and changing all links/actions/line item formats.

Regards,

Hayk

DavidSmith

Just to clarify, this restriction applies to all lists, not just numbered lists.

I hope that helps

David

Quick Links

Can you help?

Unanswered questions

How to use a different 'Current period' for different versions
I'm working on a model with three versions: Actual (Actual version), Scenario: Prognose lopend jaar (current version), and Scenario: Budget volgend jaar. For one of the calculations, the Scenario: Prognose lopend jaar version needs to use a different current period than the Scenario: Budget volgend jaar. For this, I…
one or multiple models
Does anyone have any documentation on the trade-offs of having 1 model for all components of planning (service revenue, product revenue, labour planning), vs multiple models 1 for each and a consolidation model to tie it all together?
A reminder of Bulk Copy - Current year to Prior year version for YoY analysis
A quick reminder of the Bulk Copy functionality. Bulk Copy allows you copy large volumes of data from one slice of a model to another in a single, optimised operation, instead of using formulas or imports. Use case: copy a version (RF1) into a prior year version (PY RF1) using a versions list to allow for year-on-year…