Submit a Ticket My Tickets
Login  Sign up

Integration Attribute Mappings

Ask the integration partner to provide you with the list of codes and translate values (descriptions) for the following fields.  Once you have these you can then edit the Admin Console → Integration Attribute Mappings and add all of these into the system.  Make sure you Sync to the field options screen and then execute two sets of merges as Always Institution for all of the entities to pull the data in with codes mapped to the values/descriptions that you've entered.

Also note that you should look hard at the returnRaw data from the endpoint to see which of these you need to ask the partner about.  I.e. don't ask for term.status if the SIS doesn't even have such a field.

  • Term
    • Status
  • Department
    • Status
  • Rooms and Buildings
    • Room type
    • Features
    • Campus
    • Status
  • Instructors
    • Status
    • Type
  • Courses
    • Notes (if client has note codes with translate values please provide the list. If they are free form then skip this request)
    • acadLevel
    • gradeScheme
    • locations
    • Credits.primaryComponent
    • Attributes
    • Status
    • instructionMode
    • registrationMode (if exists in SIS)
    • Type
    • Career
    • Categories (if applicable)
  • Sections
    • InstructionMode
    • gradeMode
    • registrationMode
    • sectionType
    • college
    • status
    • notes (if they have note codes and translate values then please provide. IF this is a free form field then just ignore this request)

Colleague example:

Note that after the integration attribute mappings are updated, users will need to update forms with the new select options that have populated within the template. Within curriculum, this can be done by removing then re-adding course and program template fields within forms. 

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.