If a line item name changes in the source, keep the mapping in actions so that it pulls from the new line item name automatically.
Indeed, this is a rare and quite hidden case when a rename of a line-item can generate malfunction in an import action.
Until this will be solved, it is mandatory to check if the line-item it is used as source for an import action.
It was said that this issue was solved, but it is still not solved:
https://community.anaplan.com/t5/Releases/What-s-New-February-10-2018/ba-p/28590
Issue 74688 - "When importing data between modules where a line item in the source module was renamed, data matching was based on the name of the old line item"
As an Anaplan Tenant Administrator, I need the Export functionality to be able to export all the existing Tenant Level Roles information as well as the role details, into a CSV file, So that I have the accessibility to document and report to my security team. I know this feature is successfully implemented when I can see…
Currently, only Workspace Admins in Anaplan can access certain model metadata and deployment validation panels (such as Revision Tags, Data Tags, etc.) in the Production workspace. For security and compliance reasons, we want to avoid granting admin-level access to users who only need to view this information. There is no…
Currently, Anaplan does not natively restrict number inputs to specific ranges. Users can input any numeric value, which may result in data integrity problems, especially in collaborative or decentralised planning environments. Introducing a validation capability—where model builders set upper and lower bounds for number…
