Hi,
Please see the details of my inquiry in the attachment
Regards,
When you are mapping the line items to each other, check the date mapping option to the right. This sets the date formats
As an aside, it is much better to use a unique key for the data rather than a generic numbered list.
If this data is by employee only, why not use the employee id as a code for the list. Or join the employee id with other field to create a unique record. That is a much more efficient data structure for data hubs and downstream models.
You shouldn't really be importing all of the records in the same format from the data hub directly into the main model using generic numbered lists.
David
I can see you have the time dimension in the target module.
Are you sure this error is not related to how you map the time dimension rather than the date to date import ?
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…
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…
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…
