I have to get solution like this , see below screenshot
https://community.anaplan.com/profile/sumarendla95 As because of E2 employee is a number list you must map with code insted of nameID.
Thanks
@sumarendla95 As per @jagadishdash comment do the following below
I believe this is from LV1 training. Review material on mapping by Name and Code. Generally, you will always map by CODE. A rare example otherwise is where you allow a user to enter a list item, then come back and use a module item to generate a code for that Named Item and populate CODE values for list items. So, in the above example, you are correctly using a Numbered List because Employee Names can be the same, possibly have a length that exceeds 60 characters, and last names can change (marital status, etc) . So JOHN DOE and JOHN DOE, two different employees, would be imported correctly by CODE.
@jagadishdash I do not recall the specific function or import situation but there is (unless it has been fixed) an issue where missing CODES from either a standard or number list will cause that item to not be correctly included. Therefore, it is best practice to ALWAYS use CODES on either standard or numbered lists. Additionally, CODES are extremely helpful and efficient when used as defined within the best practice material because they provide item metadata without less efficient functions. For example, list item Production Line 1 is at Manufacture Facility 5 (CODE MF5|PL1) allows a list of Production Lines to be created where line item LEFT(CODE,FIND("|")-1) provides MF5 and FINDITEM(Manufacturer,"MF5") provides the Manufacturer list item.
Cheers,
James
Thank you @TristanS @jagadishdash @James Martin - Cognizant I got my solution as per your suggestion
It's now possible to use the additional insights to have dynamic filters, however the columns in the table are fixed widths. It's quite unfortunate that the ability is added, but the layout isn't dynamic. I understand that a report is more fixed, but adding dynamic columns would really help make the management reportβ¦
There was an error rendering this rich post.
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β¦
