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"
Anaplan currently provides the ability to create versions via an Import action, and update Version settings via an Import action. Ability to use an action (of any type, Import or otherwise) to do the following: - Rename Versions - Delete Versions Business Need: As we seek to continuously improve our planning process…
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: When presenting visualizations in Anaplan, users often try to hover over lines/bars/points in the chart with their cursor to point…
Description Currently, scroll bars in Anaplan UX grids and cards only appear when content exceeds the visible area and when you hover over a card and the scroll bars appear. While this behavior is standard, it can create usability challenges for end users, especially when: Users are unsure if additional data exists beyond…
