2.3.9.1 Import Data Into DAT03 Historic Volumes module

I have been through many related threads but still couldn't resolve this. I get the error: "DAT03 Historic Volumes.Export" could not be located. I tried to remap but get the same error. I provided screenshots for more context. Thanks for any assistance!

Source_models_134458.jpg

Error_Msg__export_not_found_134458.jpg

Export_saved_view_134458.jpg

Action_view_134458.jpg

Comments

TimothyThomas

Hi @dbew ,

From your source models view, it appears you have two different Data Hubs in there, the 2nd of which is mapped to your Supply Chain model. It shows as having two imports associated with this source model, so one could be this specific import. Perhaps try changing the source model of that one to your Data Hub and see if that resolves the issue?

Thanks,

Timmy

dbew

Thanks. I mapped the "Your Name" line to the Data Hub (screenshot), but I still get the same error. I don't think I created that first source line and I don't see how to delete it. The second line appears to be mapped correctly, but the process fails on the first line.

Remap_Source_134467.jpg

TimothyThomas

That is strange. I'm afraid I'm not sure what the problem is then, as everything in your setup looks right to me. I guess my only suggestion would be to manually re-import and try resetting up the process and see if that works. Last week someone else was having a similar problem, so I'm not sure if this is a more widespread issue or not, but can't be sure myself.

Sorry to not be able to help more!
Timmy

dbew

Thanks for looking into it. I may just need to start the second sprint over again to avoid whatever is corrupted.

dbew

I created a new Supply Chain model and ran through the sprint 2 exercises again to remove any errors and got the same result. Could the error still be related to the time ranges? The Hub DAT03 Export view has a FY19 time range and the Supply Chain DAT03 has a FY19-FY20 time range. See attached. I do find the time range mapping issues very confusing.

HUB_DAT03_Export_View_Time_Range_134576.jpg

SC_Time_Range_134576.jpg

TimothyThomas

Hi @dbew ,

I wouldn't think that's the issue. As long as there is an overlapping time frame between the two, there shouldn't be an issue with it mapping the time range (in this case, FY19 is a common time frame). My modules are set up the same way.

I'm sorry this is still not working after all that extra work. I would suggest potentially posting in the Academy forum and seeing if anyone might have an idea over there: Link

Hoping someone else can help figure out what is going on! I'm stumped at this point, unfortunately.

-Timmy

dbew

Thanks Timothy, I'll try the forum. Given the number of threads, views, and years of history with this blocker, I would think the content and/or tool would get updated.

Olek P

Did you ever find out what the issue was? I have the same error

IshaanChitale

Hello All,

I am currently working on an exercise to import data into the DAT03 Historic Volumes module in my Supply Chain model L2: sprint 2: (2.3.9.1) Can someone please help me fix this import. I cant understand where I am going wrong and why it won't import. The time ranges have been selected as FY19-FY20 for the line item with the start date as JAN 19

hotessay

代写留学生作业服务还为那些需要同时完成多项任务的学生提供了极大的便利。在学期末或者考试季，学生们往往需要同时完成多个essay，并且还要为即将到来的考试做准备。

Quick Links

Recent release news

May 2025 platform releases and what’s next
Check out the latest Anaplan feature updates and enhancements in our May 2025 official release notes. The information below offers supplemental information to that post. Integrations and extensibility Preview dataset when mapping to model or selecting for transformation view in ADO When selecting a dataset to map to a…
April 2025 platform releases and what’s next
Check out the latest Anaplan feature updates and enhancements in our April 2025 official release notes. The information below offers supplemental information to that post. UX New UX for Models section in Administration The Models section in Administration has been redesigned with a more intuitive interface. Tenant…