In the Importing Data Modules Activities for Employee Details, I'm having issues matching the employee names with the source. It does not recognize the employee name in the 2nd tab ( "#E2 Employees") and therefore does not match the names. See Screen Shots.
This is because this is a numbered list vs a standard list. Because of this, the system will generate an ID for the name and you will import off of the code, while using a display name property for end users to see. Re-watch the Microlesson on importing into lists, it will discuss this exact issue under Importing Errors.
So this response explains why the problem exists, but I don't see how it rectifies the issue. If the module imports can't map the data to be imported automatically to numbered list display names, it seems to me to be a strong disincentive for using numbered lists.
Honestly, I'm having trouble really seeing the value proposition of Anaplan-managed numbered lists at all. While it's certainly valuable to have guaranteed uniqueness in one's key/code, It's often desirable for that unique key/code to not be a simple serial number starting from 1. the micro-lesson sets the code to the SKU number, and that provides enough uniqueness on its own. Systems like SAP can assign unique numbers to new master and transactional data entries (e.g., inventory material numbers and sales order numbers, respectively) within a range while still being random enough to make fraudulently fabricating a valid number difficult for social engineers/hackers.
I'd love to hear someone succinctly sell me on the value Anaplan-style numbered lists, because being unable to import data in situations like what the OP (and I) encountered would be daunting indeed if the list were an order of magnitude or two larger.
It would be indeed not feasible to map thousands of items manually. That's why we are using Codes in Anaplan, they are particularly important while working with numbered lists, for example in a case like this.
If you built up your #E2 Employees list correctly, it should have Code for each employee.
1. On Mapping Tab, you need to choose column with 'Code' from source files.
2. Then on #E2 Employees tab, you select match on names or codes and... done. All elements of your list (employees) are mapped automatically.
I can now tell you exactly why this is a point of confusion. The lessons that are linked in your post all speak directly to thelist import process and not the module import process (which is where I'm hanging up). The lessons make very clear how the numbered list import is supposed to be executed, and my list works perfectly.
It's in the mapping of the data file within the module using the correctly imported list that I was hanging up.
The module import Mapping tab asks for the source data to match the target, which is this case is given here:
Note how strongly the UI cues the user to incorrectly select Column 2 for the source identifier by not only matching the column name (which is admittedly coincidental here), but also the fact that it prompts the user to select a column that contains actual names rather than codes as found in Column 3. This confusion is further confounded by the Details specifically prompting for the Code to be handled by the second source identifier.
In the linked microlessons, the training materials take pains to emphasize this... I'll be kind and call it a quirk... of the interface during the list import process, but there is no such analogous emphasis for how to modify things during the module data import process.
Ideally the UI would recognize that it's trying to populate a numbered list and prompt the user to map to the code data and not the display name data, and the training example would compel the user to "get it right" before moving on by providing, e.g., two employees in different departments with the same name. I moved on after manually mapping in large part because the training materials didn't force the issue of resolving the non-uniqueness at the time. Had it done so, I would likely have tinkered around and tried using the code against the guidance of the UI to clear the errors.
I'm trying to move on and finish the L2 curriculum, but it would be nice if someone else would be so kind as to reply with the relevant microlesson that talks about module data imports against a numbered list.
I hope the above makes my (and I suspect @davidmccarty 's) sticking point clear and why the referenced microlessons don't speak to it.
Thankfully this is all moot to me now, as I see how to successfully execute the import, credit to @filip.sypniewski.
I understand your point. I am pretty sure that I followed a video once in which import into modules was explained in details. I cannot find it at this moment, but maybe @ChrisMullen will identify it quickly. I think you are free to share also your feedback with Academy team and help make the courses better for everyone!
In the file that I just downloaded from Level 1 course and tried to load in to my list, I did however not see the second column "#E2 Employee". Can you check that and download the file again? Indeed it might be misleading for you. I can see Column 2 being a Code.
At this moment, sharing the article in which import into modules with numbered list is also explained, but I will get back if I find corresponding video.
I'm struggling to understand what I'm supposed to do about the date formatting as well (other than just change it in the source data). In the videos, there is a Time tab that you can access if Time is a dimension, but here it is not.