A case where general lists unique key were mapped to name or code now wants to map for code

Gudivadadasari · 2025-02-05T15:22:05+00:00

There was an error rendering this rich post.

A case where general lists unique key was mapped to name or code now company wants to map for code. There are 300 dimensions need to have this change. How the Downstream impacts for this change ? What are the cautious things need to keep in mind before making this change ? Please suggest .

Accepted answers

devrathahuja

Hi @Gudivadadasari ,
Take an export of the current list & ensure that the existing codes & codes in the new file/source are the same (Any changes or mismatch in codes will lead to creation of new members)

If the codes are the same then the only impact would be change in name of the member.

As @seymatas1 suggested, if size isn't an issue giving this a try in a copy module would help you ensure you do not disrupt anything.

seymatas1

Cautions:

Copy and archive the model before making changes.

2. Create a revision tag before starting. Use the last history ID in the revision tag.

3. Don't delete list items. This will delete all module data for that item.

4. As @devrathahuja mentioned, do not create duplicate list items.

5. Push the changes to a test model first.

6. If your list is a production list, make the import action change in the dev model, test it in the test model, and rerun the action in the prod model.

I hope this helps.

Seyma 🌷🙂

All comments

seymatas1

Hi @Gudivadadasari,

If you have enough workspace, you can create a test model from the dev model and push the changes to the test model. Check its impact before making the change to the prod model. If you're comfortable, sync prod with dev.

I hope this helps.

Seyma 🌷🙂

devrathahuja

seymatas1

Cautions:

Copy and archive the model before making changes.

2. Create a revision tag before starting. Use the last history ID in the revision tag.

3. Don't delete list items. This will delete all module data for that item.

4. As @devrathahuja mentioned, do not create duplicate list items.

5. Push the changes to a test model first.

6. If your list is a production list, make the import action change in the dev model, test it in the test model, and rerun the action in the prod model.

I hope this helps.

Seyma 🌷🙂

Quick Links

Can you help?

Unanswered questions

Importing Ragged Hierarchies
Hello - I have a 2 level ragged hierarchy (yes, it's a chart of accounts), that for reporting purposes is used in 4 different models (yes, it's a P&L). What is the best way set this to allow one to be the "source of truth" and then import between the four models without creating actions that include ignores? It seems like…
Where can I find export file after running export process using machine task in a workflow?
I am testing export actions using workflow but its not generating any file when I am running the workflow, but the same process is generating export file when ran from the Actions→Process section. Is their any issue with the workflow functionality? Also, If I want to generate a file after completion of workflow and pull…
Automating Flat File Uploads to Anaplan Data Orchestrator (ADO) – Best Practices and Methods
Hello Anaplan Community, I am seeking guidance on the most effective ways to automatically upload flat files to Anaplan Data Orchestrator (ADO). Currently, our process involves loading flat files to an Anaplan Datahub using Anaplan APIs and custom Python scripting. With Anaplan Data Orchestrator's capabilities for data…