nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Import action failed while running through Cloudworks

wolframarnab

According to the given screenshot, error thrown by Cloudworks is - "Hierarchy import has both Name and Code unmapped".

Although, manually the import action is running fine.

Cloudworks Failure.png

Need some help.

Thanks,

Accepted answers

All comments

TristanS

@wolframarnab Looks like the underlying Anaplan action for CloudWorks Process "21.1 Import .. " has lost its mapping. This can occur when the module line item it was originally mapped against has been deleted. You will need to remap the code or name for the list. You may even need to create a new line item for it to map to.

Below are details to get to the underlying Anaplan action

Select CloudWorks in top left menu. Then Click "Integrations & Processes". Then click on the Process "21.1 Import .. ". Then Click on "…" on the right most of the process. It should display options in yellow below.

2. Click on "Edit". The "Edit - Process" dialog should display. Take note of the Model and Action (highlighted in yellow)

3. Open the model in step 2. Then Go to the Actions tab to find the action specified in step 2. The click on Edit. You will probably find the Name and Code blank. You will need to remap that

TristanS

My bad just noticed you mentioned that import action runs ok when run manually

Quick Links

Can you help?

Unanswered questions

Introducing Anaplan Toolkit: side panel for model details, exports and model lock tracking
Hi everyone 👋 If you build or maintain Anaplan models, you've probably hit the same walls I kept hitting. Some basic questions about a model's structure have no single screen to answer them. You end up clicking through modules and pages one by one, or writing API scripts just to get a list. These were the gaps that…
How to handle an Entity Structure change effective from January 2026 in Anaplan Consolidation & Repo
Hi Everyone, We have a requirement in Anaplan Consolidation & Reporting (Fluence) where the Entity Structure needs to change effective January 2026. The key requirement is that the existing entity structure should continue to be applicable for all reporting and consolidation periods through December 2025, while the new…
Anaplan ⇄ Google Sheets pivot tool — feedback welcome
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…