Level 1 Model Building SYS08 Employee Details Import Issue
We are asked to import Emloyees.csv into SYS08 Employee Details and I am unable to get the names in the list to match on the names in the employees list that I already have in. I checked and I have the data type as "Text" listed within the SYS08 module, and the .csv has the data in that column listed as "General". I also tried changing that to "Text"; neither work. I can do it manually but it will take a long time.
Is there something I'm missing or should consider?
Below is the mapping of the line items and the Grid View after loading.
1) The Code cells are blank. What item should be mapped to Code?
2) Are Code, Name, Department, Country, Start Date, Leave Date, Current Salary, Commission % supposed to be in Rows or Columns?
In the Model downloaded as per training activity, these are displayed as Columns. Wondering if there are any steps missing at this point or are there future activities that result in these being displayed as Columns.
The code should be derived via a formula, no source items need to be mapped to the "Code" line item for the import. The code is related to the #E2 Employees list, you will need to use the appropriate formula to return the CODE for a list ITEM.
To your second question, you can change the view of a module by selecting Pivot, moving the elements and then saving the view as default. From a functionality perspective, it doesn't matter if the items are in rows or columns (the calculations will work regardless). The question you must ask yourself is: what view makes the data easiest to read (Line Items in Columns is likely the best bet here).
Hope this helps! Shout if you have any more questions.
I was stuck with this too and I'm at a similar stage in the training. So the output in the screenshot above which @Star has shared is correct?
Also, I populated the code line item with a name and the only way to fix it was by deleting the line item and inserting a new Code line item again in the module. I reimported again by not ignoring code in the mapping (not sure if this step was required again though).