invalid date identifier have validaed the date formats in the file but import fails with same error
@PrevContributor wrote:This error indicates that the date formats in the file you are importing are either not matching what is in your module or they are not mapped correctly on the Time tab in the import. Let's assume that your are working with a monthly module and you are in 2013. The Anaplan module will show Jan 13, Feb 13, etc. as the months. Here are some examples of what the dates may https://krogerfeedback.nl https://talktosonic.onl https://talktowendys.vip https://whataburgersurvey.onl look like in your import file and how you would set the Time tab to map them to Anaplan correctly: Jan 13, Feb 13, Mar 13 - Match Names 1/1/13, 2/1/13, 3/1/13 - Date and choose Patterns with Separators M-D-Y 01012013 - Date and Choose Fixed-position Patterns MMDDYYYY See more details about mapping dates here: https://community.anaplan.com/anapedia/data-integration/import#mapping-timescale.
thanks for the awesome information.
Hello, Does anyone know any workaround or a solution to be able to enable the hierarchy filter in new ux when the brought forward option is selected in backend? I do not see the above hierarchy filter option if I enable the brought forward for a line item-
Hi I'm looking to speak to people who have used/are using the Docusign integration in their business. We are exploring the possibility, but we find the current setup quite limiting in terms of how an end user would interact with the integration, but also issues with concurrency and number field formats. Would appreciate…
A quick reminder of the Bulk Copy functionality. Bulk Copy allows you copy large volumes of data from one slice of a model to another in a single, optimised operation, instead of using formulas or imports. Use case: copy a version (RF1) into a prior year version (PY RF1) using a versions list to allow for year-on-year…
