What could be the rootcause, and how could we fix it ?
This error typically indicates that the underlying import action is encountering duplicate list item names/keys. Check the source data for duplicates, validate the import mappings (preferably using Code as the unique identifier), and review the import log by running the action manually to identify the offending records.
Could you share a bit more context? Are these duplicate names showing up in Anaplan CloudWorks itself, or in the source/target data? In many cases, duplicate names are caused by duplicate records in the source system, using a non-unique field as the key, or an import action that's creating new records instead of updating existing ones. If you can share the import setup or a screenshot of the error, it'll be much easier to pinpoint the root cause.
We have an Integration Process in Anaplan CloudWorks created by User X - No WSA (originally Full Access with top-level Selective Access, now changed to Planner Read Only with Selective Access unchanged) and scheduled by User Y - with WSA , who also created the Integration Flow. Internal (Full Access) is enabled within the…
We've been building a tool called aplan4sheets and we'd genuinely like input from this community — both on what we've built so far and on what we should prioritize next. The problem we set out to solve: Anaplan's Excel add-in is Windows-centric, and there's no real native way to pivot Anaplan data in Google Sheets. We…
We are looking for Anaplan end-users to provide feedback on their experiences with the Excel add-in. Interested individuals will respond to this 5-minute survey to help us understand personal needs and behavior when using the add-in. The feedback provided by survey takers is essential to the roadmap of Anaplan's products.…
