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"
While the Model Map functionality already exists in Anaplan, it becomes difficult to navigate when working with large models. I would like to see enhanced support for full export capabilities of the model schema (DISCO). This would greatly streamline documentation efforts and save time when capturing model status across…
I'd like to request implementing a formal notification system for upcoming platform changes and updates. This would be incredibly valuable for the Anaplan community for several reasons: Real Impact Example:Recently (Sept 2025), an unannounced Cloudworks change restricted .csv000 file imports. This resulted in: Failed…
We recently noticed that users that have enabled passwordless authentication through Microsoft are no longer able to login to Anaplan via single sign on. After entering a ticket via Anaplan, it seems that this is a hardcoded platform parameter which specifies that authentication must occur through a password-based feature…
