Hi Team, I'm unable to understand the import below shown is my mapping.
@Rohs28
Your mapping is correct.
In your second screen shot the item "Montreal" isn't mapping because they are spelled different in your L1 and L2 models. Importing based on code can help eliminate this issue, especially in cases where names might change.
In your last screenshot you can select the option to "Map items manually" and then "Ignore" the code since it isn't needed. It's fine to leave as is, you'll just get a message that the import ignored the unmapped item.
Check out the latest Anaplan feature updates and enhancements in our February 2026 official release notes. There you'll find information on: User Experience Board Insights Panel Management Reporting on mobile Custom action buttons on mobile Modeling experience Four digit calendar Forecaster Holiday calendars UX pages…
Check out the latest Anaplan feature updates and enhancements in our January 2026 official release notes. The information below offers supplemental information to that post. Dataspaces in Anaplan Data Orchestrator Dataspaces are partitioned areas of a tenant-wide Anaplan Data Orchestrator instance. Integration…
_144890.png "Screenshot (27).png")
_144890.png "Screenshot (28).png")
_144890.png "Screenshot (29).png")
_144890.png "Screenshot (30).png")
_144890.png "Screenshot (31).png")
