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"
Idea Description As a model builder, I want dependent dropdown rules to be enforced consistently across all data-entry methods, so that users cannot enter values that would otherwise be unavailable through the configured dropdown selections. Example of Enhancement I'll know this is successful when values that do not meet…
Problem In Management Reporting, the number of columns in a Table card is fixed when the card is created. When a dynamic filter returns a different number of items (e.g. fiscal years depending on the selected Version), the card does not adapt: If the card was created with few columns, additional items (e.g. FY29) never…
Allow end users to apply multiple sort levels on a single grid in UX pages, so they can organize data across several dimensions without workarounds. Thank you,
