Instructions for requesting choice value mappings using the unmapped values csv files
The conversion tool only maps matching values. For example, if you had a client category of Bronze on your source site and Bronze is also a client category value on your destination site then this would have been converted for you.
If however you had a client category of Bronze on your source site and Bronze is not a client category value on the destination site then this value will appear in the Unmapped Values file as it was unable to be converted.
It is also important to note that the value format has to match exactly for values to be converted. For example, if you had a client category of Bronze on your source site but the client category value on the destination site is bronze, this would not be converted as it is not an exact match (first letter is upper case in one value and not in the other).
Please keep this in mind when completing the Unmapped Values file. Choice Values that were not mapped during the conversion can be mapped afterward.
If you want us to map any of the values listed in the Unmapped Values file, you need to update the file as instructed below and return it within 2 working days.
Step | Details |
1. Filter Required Fields |
Apply Filters to the file to make it easier for you to update it with the required mapping value. Use the field column to identify which fields you would like to request mappings for. For example, if you would like to request client category mappings then only tick client_catergory when filtering the field column.
Filter Column D (Field):
Client_Category Field Example:
Filter Result: |
2. Update Column E (Value) with the required mapping value |
Values in Column E should be replaced with the required mapping values from the destination site. It is imperative that the values you enter are available for that particular field in the destination site and the format is exactly how it appears in XPLAN for that field. The best approach to update the values is to use the filter for the value column and filter each value one at a time and bulk update all rows under that value.
Update Column E (Value):
Filter Value Column and only tick one value at a time:
Filter Result: Update all listed rows for the ticked value with the required mapping value from the destination site. In the example below I have updated the value Upper Case B to a Lower Case b. |
3. Open all filters and repeat Step 1 & 2 for all required fields |
It is very important that you do not change data within the other columns and do not delete any data within the file (apart from replacing the values that you are updating in the columnE) as this will cause the requested mappings to not be applied correctly. Also, please save the file in CSV format only. Saving the file in any other format will cause the id’s to change and we will no longer be able to process it. |
Further information on Conversion Mapping here
If your data requires custom fields these will need to be built into XPLAN prior to signing off on the conversion. Once the fields have been built you will need to supply the field mapping via the unmapped values file to dictate which fields go where in the XPLAN site. As each site can be different there may be different mapping required. Please note not all custom fields are necessarily required and you should contact your site administrator.
Further information on Custom Field Mapping here
When converting your Tasks to a new XPLAN site you need to ensure that you provide instructions via the unmapped values file for the correct mapping of Tasks. If the destination site does not have the relevant Task Type and Subtype that you require and there is no corresponding Task Type and Subtype that you can use then you can create a new Type or Subtype. Please contact your Site Administrator. Please note the Task Type and Subtype should be provided in a seperate CSV as the standard unmapped values file only caters for Task Type and not Sub Type.
Further information on Task Type-Subtype Import here
When converting your Notes to a new XPLAN site you need to ensure that you provide instructions via the unmapped values file for the correct mapping of notes. If the destination site does not have the relevant Note Type and Subtype that you require and there is no corresponding Type and Subtype that you can use then you can create a new Type or Subtype. Please contact your Site Administrator. Please note the Note Type and Subtype should be provided in a seperate CSV as the standard unmapped values file only caters for Type and not Sub Type.
Note Type and Subtype CSV
1. You will need to filter the A column in the 'unmapped_values.csv' to show only 'entity_note' and 'task'.
2. Cut and paste each column that is the same as the columns in the image below into the 'Note & Task Type-Subtype import.csv'.
3. You should now have a spreadsheet that contains only 'entity_note' and 'task' group rows. The next step is to look at column F labelled 'value1' which is the type of note or task for that row. You will also need to look at column H labelled 'value2' which is the subtype of note or task for that row.
You will then need to look at what is currently in the cell and match it to what type/subtype options exist on the target site.
Note: column E is 'type' for note but 'taskkind' for tasks.
It is very important that you do not change data within the other columns and do not
delete any data within the file (apart from replacing the values that you are updating
in column E and H) as this will cause the requested mappings to not be applied
correctly.
Also, please save the file in CSV format only. Saving the file in any other format will
cause the id’s to change and we will no longer be able to process it.
Further information on Note Type-Subtype here
IRESS Wealth Management | XPLAN Transitions | Conversion Field Mappings