In the Mapping step, you specify which fields from your source file are imported into which Core+ database fields. The Young Person Mapping page is divided into sections that mirror the structure of the Core+ database, and you can expand each section. Unmapped source fields also appear so you can see what still needs mapping.
Mapping controls
Use these options to load, save, auto-map, or remove mapped fields.
Click Load Mapping to load previously saved mappings. Saved mapping files can only be used if the import file uses the same field names; new, changed, or additional field names will not be mapped. Legacy mapping files can still be used.
Click Save Mappings to select a folder and filename for your download, if your browser supports this.
Click the lightning bolt icon on a section to auto map its fields.
Click the delete icon to remove a mapped field.
Mapped fields
Use this option to add a new field mapping between your source file and the Core+ database.
Click + Add Mapped Field. The Add Mapped Field dialog opens.
Select a Database Field from the drop-down list.
Select the source column that contains the data, or a static value to use:
Source Column: To manage blank values, select the Use a default value when the value in the source column is blank checkbox, then select the value from the drop-down list.
Static Value: Enter a value that is common to all records but not in your import file, such as a lookup code or a specific date. The import updates all records to that value. This is useful when the data is missing from the import file.
Some fields offer extra options:
Special value: Select the Special Value radio button, then choose Current Date or Current Date/Time.
Search: Enter the detail into the search field; when you enter a partial entity name, matching results appear. Select the required record to populate the static value.
Advanced: Click Advanced, then choose how to apply the values: Always, which overwrites all values and blanks, Only if the new value is not blank, or Only if the existing value is blank.
đ Note: Some mapped fields are required to maintain the Core+ database's relational and key integrity. These are highlighted red, and must be mapped.
Destinations
Use this section to map the destination for each Young Person record in your import file.
Select Destination from the Young Person Mapping, then click + Map Destination.
Map any required fields.
Select one mode: Create a new destination, or Update the current destination. Only one mode can be selected.
Intended destinations
Use this section to map the intended destination for each YP record in your import file.
Select Intended Destination from the Young Person Mapping, then click + Map Intended Destination.
Map any required fields.
To skip the import when a YP already has an intended destination, select the Skip import when YP already has an Intended Destination checkbox. You can refine this to only if the existing intended destination is open and has no closed date, or only if it is newer than the record to be imported.
September Guarantee
Use this section to map the September Guarantee fields for each YP record in your import file.
Select September Guarantee from the Young Person Mapping, then set:
School Year: Select Auto-detect school year from date of birth, which uses the YP's date of birth to decide Year 11 or Year 12, School Year 11, School Year 12, or Use mapped data which derives the guarantee type from the data mapping.
Default recorded by: When you have selected a default value during mapping, select who the default was recorded by. This updates the Default Recorded by fields in Core+.
Duplicate Guarantee Action: Select the action to take if the YP already has a guarantee record for the specified year. Select the Skip when offer date and status match existing guarantee checkbox to exclude YP records already imported where the offer date and status match. If you select Update existing guarantee record, only records with the same Provider, Course, and Year are updated; where there are multiple, the most recent is used.
Mapping validation
When you have finished mapping, click Next. Validation then takes place:
Errors are shown in red and must be resolved before you can continue.
Warnings are shown in orange; review them, but you can continue if needed.
Click into a mapping to view its errors or warnings.
If a date is incorrectly formatted in the source file, it is shown in the Source Value column, with the number of affected records in the Record Count column. Enter the date in the correct format in the Resolved Value date field, then click Update.
If incorrect lookups are mapped, the Source Value column shows the incorrect values from the source file and the Record Count column shows the number of affected records. Select the correct value, then click Update.