Element451Integrations Guide

Populi UAT / Field Mappings

Updated Article

Testing the Populi integration typically happens in two phases:

  • Element451 → Populi
  • Populi → Element451

Element451 → Populi testing is usually completed first. Populi → Element451 testing should only be completed if the partner has requested data to sync from Populi back into Element.

Both phases should begin after the required Populi configuration has been completed, API access has been confirmed, and test records are available.

Triggering the Integration

During testing, integrations should be triggered manually. Once live, they can be automated.

For instructions, see How to Sync Records (Populi)

Testing Element451 → Populi#

Preparation#

Create test student records in Element451 with applications. These records should represent a wide range of scenarios used by your institution.

Note: These records should be removed before go-live as they are test records.

Testing#

Follow the steps in How to Sync Records (Populi) to trigger a sync.

Validate Data in Anthology#

Once a record has synced successfully:

  • Review the record in Populi
  • Compare values using the Field Mappings section.
  • Validate:
    • Element451 fields (slugs)
    • Corresponding Populi fields

The Field Mappings reflect the standard integration configuration. If your implementation includes customizations, use this as a baseline and add any additional validation checks as needed.


Field Mappings#

Below is an overview of the Element451 fields (slugs) and corresponding Populi API fields included in the standard integration.

Element Profile FieldElement SlugPopuli Field
Populi Iduser-identities-populiidid
School Emailuser-identities-school-emailemail (school)
First Nameuser-first-namefirst_name
Last Nameuser-last-namelast_name
Middle Nameuser-middle-namemiddle_name
Former Last Name(s)user-former-last-nameformer_name
Preferred First Nameuser-preferred-namepreferred_name
Name Prefixuser-prefix-nameprefix
Name Suffixuser-suffix-namesuffix
Emailuser-email-addressemail (school)
Home Phoneuser-phone-home-numbernumber (home)
Cell Phoneuser-phone-cell-numbernumber (home)
Social Security #user-ssnsocial_security_number
Date of Birthuser-dobbirth_date
Genderuser-gendergender
Are You Hispanic/Latino?user-race-hispanichispanic_latino
Your Raceuser-race-categoriesrace_id
Address Line 1user-addresses-street1street
Cityuser-addresses-citycity
Stateuser-addresses-statestate
Zip/Postal Codeuser-addresses-zippostal
Countryuser-addresses-countrycountry
Country of Citizenshipuser-citizenship-countrycountry (ID)
Notesuser-notes-note-bodycontent
School Nameuser-education-schools-namename
CEEBuser-education-schools-ceeb—
Start Dateuser-education-schools-startstart_date
End Dateuser-education-schools-endend_date
Graduation Dateuser-education-schools-graduate_datehighschool_graduation_date
App Submitteduser-applications-submitted-timesubmitted_at
App Starteduser-applications-registered-atstarted_on
Majoruser-applications-majorspecialization_id
Termuser-applications-termacademic_term_id
Degreeuser-applications-degreedegree_id
Campususer-applications-campuscampus_id
Academic Loaduser-education-academic-loadexpected_enrollment

Testing Populi → Element451#

Populi → Element testing should only be completed if the partner is using inbound sync from Populi to Element.

Preparation#

Identify the records you want to test in Populi.

  • use records previously synced from Element451 → Populi
  • make controlled changes in Populi, such as phone, email, address, demographic, or custom field updates

We recommend testing at least 5–10 records to cover a variety of scenarios.


Request or Trigger a Sync#

Notify Element staff via Basecamp with the records to be synced.  Provide them a timestamp of BEFORE you started making the record changes.

Validate Data in Element451#

Once the sync is complete:

  • review the records in Element451
  • confirm that the existing records were updated correctly

Use the Field Mappings section to validate field-level accuracy.


Field Mappings#

Below is an overview of the Element451 fields (slugs) and corresponding Populi API fields included in the standard integration.  Additional fields/properties can be set/read based on a partner’s SOW.

Element Profile FieldElement SlugPopuli Field
Populi Iduser-identities-populiidid
School Emailuser-identities-school-emailemail (school)
First Nameuser-first-namefirst_name
Last Nameuser-last-namelast_name
Middle Nameuser-middle-namemiddle_name
Former Last Name(s)user-former-last-nameformer_name
Preferred First Nameuser-preferred-namepreferred_name
Name Suffixuser-suffix-namesuffix
Emailuser-email-addressemail (school)
Home Phoneuser-phone-home-numbernumber (home)
Cell Phoneuser-phone-cell-numbernumber (home)
Social Security #user-ssnsocial_security_number
Date of Birthuser-dobbirth_date
Genderuser-gendergender
Are You Hispanic/Latino?user-race-hispanichispanic_latino
Your Raceuser-race-categoriesrace_id
Address Line 1user-addresses-street1street
Cityuser-addresses-citycity
Stateuser-addresses-statestate
Zip/Postal Codeuser-addresses-zippostal
Countryuser-addresses-countrycountry
Country of Citizenshipuser-citizenship-countrycountry (ID)
School Nameuser-education-schools-namename
CEEBuser-education-schools-ceeb—
Start Dateuser-education-schools-startstart_date
End Dateuser-education-schools-endend_date
Graduation Dateuser-education-schools-graduate_datehighschool_graduation_date