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"
We have discovered that Line Item Subsets cause unexpected behaviour in Polaris: their mere existence adds significantly to model size and calculation demand. This overhead is undocumented (it appears in neither Anapedia nor the Planual) and is not visible to the model builder during building. The only way to detect it is…
From my perspective, the Anaplan community has three purposes: Customers/Partners to share feedback with Anaplan so the roadmap can be designed with those who actually use—and pay for— the product(s) in mind. Status - Mixed success leaning towards failure— as of about 4 years ago, Anaplan stopped interacting with and…
Currently, when approvers are assigned dynamically from a module line item, a Decision Task proceeds as soon as any one of the assigned users approves it. Please extend the “Require approval from all assignees” option, which is currently available for manually selected approvers, to dynamically assigned approvers as well.…
