Hi All,
Has anyone completed exercise # 4.8.2 Activity: Import Data into E2 Employees# List? I am not able to procced with this, can anyone j
@nilvshah
Good callout. The first step is to recognize that E2 is a "Numbered" list. Meaning, it doesn't need a Name because Anaplan will assign a number to it. So your mapping of the file should look like this:
Thanks so much... it works for me...
Explained so well, eloquently and succinctly @JaredDolich!
This was really helpful.
@JaredDolich
what do you mean anaplan will assign a number to it? It seemed like that's what we did when we used the code (column 2)
@anniecommune
Hey! Great question, my answer was a bit ambiguous. Let me 'splain.
Every list has two unique identifiers. A name and a code. Both are TEXT formatted. When we create a numbered list we allow Anaplan to fill in the name identifier for us, in this case it's number-looking even though it's really text. So the first three list items would be given #1, #2, #3, respectively for their names. When we use a numbered list, you cannot use a column in the input file that refers to the name because Anaplan has already put a value in there. So, we have to use code instead.
In this example, with employees, we cannot use the employee name because Anaplan has no unique record that refers to the employees name. We have #1 and a code, presumably their employee ID. So when we import data, we must import using the code not the name.
Hope that helps!
Hi Community, I’m encountering an issue where an export created in Anaplan is missing column headers when retrieved via the API. However, when I manually run the same export from the Actions tab, the downloaded file includes the headers. Has anyone experienced this behavior before? I’d appreciate any insights into the root…
When importing data from a Data Hub to another model, I'm seeing values in the target model that don't exist in the source. For example, seller assignments are being tagged with subregions that aren't present in the source data - some assignments are missing expected tags, while others are mapped to seemingly random…
Hi all, I, as an Anaplan workspace administrator, am working together with a Fabric team to export data from Anaplan to Fabric via Anaplan API and Postman. We have a problem where all Anaplan exports are visible in Postman but when trying to connect to SOME of them, we get message "404, Not found". Below screenshot showing…
