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

Gudivadadasari
Gudivadadasari
in Modeling

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 .

Best Answers

  • devrathahuja
    devrathahuja
    Answer ✓

    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
    seymatas1
    Answer ✓

    Cautions:

    1. Copy and archive the model before making changes.
    image.png

    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.

    image.png

    I hope this helps.

    Seyma 🌷🙂

Answers

  • seymatas1
    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 🌷🙂

Categories