Calculated Codes using Attributes - Best Practices
We are working on a project to migrate from an Employee Hierarchy to a Position Hierarchy in Anaplan and are looking from some input from the community on Code Creation best practices. Since we do not have a good external source of data for position code, we've decided to create our own Position code within Anaplan.
At first we thought of creating a calculated code based on the position attributes; e.g L3-NA-SW-01 for a level 3 manager in the SouthWest (SW) Region of North America (NA).
However, in our POC model, after creating the hierarchy codes this way, we realized that changes to the hierarchy structure would either require the codes to be refreshed based on the new attributes (e.g L3-NA-SW-01 becomes L3-NA-NE-01 after a re-org to the NorthEast region), or else the codes would no longer align to the latest position attributes.
Is it worth the effort to use attribute based codes if every time the attributes change we have to run actions to update the codes in all the downstream lists? Or is it just simpler to go with a system generated code that doesn't require updates after its creation?