Map custom fields to integration equivalents
Education management integrates with various services that expect shared data to be formatted in a certain way; to accommodate, Platform Managers set up mappings to associate specific custom fields with integration equivalents. The result is that data sent to and returned by these integrations is consistent and corresponds with the conventions your school establishes.
To start, navigate to Core, select Settings in the navigation, and then select Integration mappings.
To map custom fields to integration equivalents:
-
Select a field under one of the integration subheadings. The fields listed under the type heading are created by your school.
-
Identify fields that are Inactive, not mapped and select edit .
-
Under Mapping, select a corresponding field from the drop-down. The integration currently supports the fields listed under the Mapping drop-down.
For example, for OneRoster - Gender, map 'Male' to the 'Male' option in the drop-down.
-
Select Save.
It is possible that some of your custom fields cannot be effectively mapped to fields supported by an integration; in these instances, the data for that field is empty. For example, OneRoster integrations do not currently support custom genders; therefore, when querying for a list of students, the ‘Gender’ for students with custom genders will be empty unless you map it to one of the currently supported OneRoster genders.
Note: After you configure Integration Mappings for IPEDS, wait until the following day to take further action. The mapped data (IPEDS gender, IPEDS race, and IPEDS withdrawal reason) is updated in the lists overnight. See IPEDS List Guide for details.
Note: After you configure Integration Mappings for the National Student Clearinghouse (NSC) or National Student Loan Data System (NSLDS), wait 24 hours to take further action. The mapped data is updated in the lists and used to logically determine the value of calculated fields, such as NSC Race/Ethnicity. See NSC List Guide and NSLDS List Guide for details.