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"
Description: In the Anaplan UX, scroll bars—especially in grids and dashboards—can be difficult to see and interact with. The current scroll bars are thin and often blend into the background, making navigation cumbersome. Suggested Enhancement: Increase the default width of scroll bars across the platform. Improve contrast…
In as much detail as possible, describe the problem or experience related to your idea. Please provide the context of what you were trying to do and include specific examples or workarounds: Below table is an example from a fictional Position Planning application. The left column shows items of a dimension called Position.…
We have recently identified a potential issue in the Anaplan platform related to workflow deletion not being captured in the Tenant Audit Logs. While the creation and modification of workflows are being appropriately logged, we have observed that deletion events are missing from the audit trail entirely. This gap poses a…
