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; } } }

Getting Invalid date format while data import into module

Jerin_KJ

hi,

my source file contain time in format 201901 201902.. etc as line item. while importing i am getting error as above .

which time format i have to select.? adding source file below.

please help to resolve the error.

Thanks

Jerin

Accepted answers

All comments

Misbah

@Jerin_KJ

In Time Window of an Import use

Periods ->Fixed Position Patterns->YYYYMM option

Here is the full article on this topic

[SCHEDULED] Untangling Anaplan Time Mapping in Imp... - Anaplan Community

Misbah

Jerin_KJ

Hi Misbah,

Thanks for reply. I will check your solution and get back to you.

another question: should source file date format match with the date format target. In my case Target file contain Time dimension in fiscal Year format.

Thanks

Jerin

Misbah

@Jerin_KJ

Please read the article I have elaborated most of the cases there and if it doesn't fit anywhere you can use Custom format. Do let me know if you need any help on that.

Misbah

Jerin_KJ

Thanks A lot . it worked for me.

ChadnrarACMA

Hi @ Jerin_KJ Thanks a lot to raise this mind boggling issue

Kind Regards

Chandrar

MuralliS

@Misbah Unable to find the discussion

Misbah

https://community.anaplan.com/discussion/81611/untangling-anaplan-time-mapping-in-imports

Quick Links

Can you help?

Unanswered questions

Anaplan XL Forms Error
Does anyone also get this error when opening the Forms in Anaplan FCR? I am downloading Investment Registry from the app but I cannot open it in Anaplan XL. How did you fix this issue?
Forecaster Advanced Explainability — time-phased writeback into a Time-dimensioned module: expected
Hi all, I'm using Forecaster's Advanced Explainability export ("Send to Anaplan") and I'd like to confirm the intended behavior and the correct interpretation of the results. Context The Advanced Explainability data form requires a Time dimension, and it writes feature values per period into a target module dimensioned as…
L3 Sprint 2, User Story 3.3 Q1 Quarter Allocation
Hi Community, It appears that values shown here for Q1 are assuming 29 days in Feb 25, when there are actually only 28. My values tie out for all Quarter values and all months shown from Apr 25 forward, and it's not possible for only a single quarter/finite range of months to differ with formula-driven values: Please…