Integration Mapping Lists | Enrollment | PowerSchool SIS and CCLR

Different systems can use different values for the same information. For example, a Student Information System might use MOM for a relationship, while Enrollment needs Mother. An Integration Mapping List acts like a find-and-replace rule: it checks an incoming value and substitutes the value Enrollment needs before placing it in a form field. You can reuse a list wherever that translation is needed within the same Solution.

Integration Mapping Lists are managed in Configuration – General – Integration Mapping Lists in the Customer Admin Portal. District Admins with the Configuration role or Super Admin access can create and manage lists. Other District Admins who can edit a Data Source field mapping can use an existing list.

Lists can also be created when an older import configuration is migrated. The system converts processing rules it can represent as value pairs into Integration Mapping Lists. Rules that need logic beyond a fixed set of value pairs use a Script transformation instead.

Create or edit a list

Each list has a name, one or more value pairs, and a rule for values that are not in those pairs. To create or update a list:

In Integration Mapping Lists, select Create List to start a list, or select a saved list to edit it.
Enter a name. Names are required, limited to 100 characters, and must be unique within the Solution regardless of capitalization. You can rename a saved list.
Add a row for each translation. Enter the incoming value under If value is and the value the form should receive under Replace with. You can reorder the rows.
Under For values not listed below, choose what the system should do when an incoming value has no matching row.
Select Save.

Fallback values

The fallback applies only when the incoming value does not match any If value is entry. It does not change the result for values that have a matching row.

For example, suppose the list is used by the Data Source field mapping for c3_Relationship. These entries normalize several source values to the relationship value Enrollment expects:

If value is	Replace with
`Step-Parent`	`Stepparent`
`Stepmom`	`Stepparent`
`Step Mom`	`Stepparent`
`Step Parent`	`Stepparent`

All four listed values become Stepparent. If the incoming value is Foster Parent and it is not in the list, the selected fallback determines what goes into c3_Relationship:

Fallback option	Result for `Foster Parent`
Keep original value	`Foster Parent` stays in the field.
Set to blank/empty	The field is left blank.
Set to a value	The field receives the value entered under Other value, such as `Other`.

Deleting a list

Deleting a list permanently removes it. If a Data Source field mapping still refers to the deleted list, validation reports: “The selected integration mapping list is no longer available.”

How a list changes incoming values

When a Data Source imports or pre-populates a field, it checks the incoming value against the list’s If value is entries. Before comparing, the system removes leading and trailing spaces, and it treats differences in capitalization as a match. When a value matches, the system puts the paired Replace with value into the form field. That replacement can be empty.

If no pair matches, the list’s fallback rule determines what goes into the field: keep the incoming value, use the specified Other value, or leave the field empty. This also applies when the incoming value is empty, and the list has no empty If value is entry. An unmatched value is not an import error by itself, so it does not invalidate the field or cause the record to be skipped. The same rules apply to Data Source imports and Pre-Populate on Demand.

Predefined Lists and Integration Mapping Lists

For an explanation of how Display, Stored, and Integration values work in a Predefined List, refer to Predefined Lists.

An Integration Mapping List is for transforming values as data enters Enrollment. It pairs incoming values with the values Enrollment should use. Its key advantage is the fallback rule: when an incoming value has no pair, the District Admin can choose to keep it, replace it with a set value, or leave it blank. A Predefined List’s Integration value can identify a known value associated with a form choice, but it does not define what to do with every value that has no match.

That fallback is useful when source data varies or is incomplete. Integration Mapping Lists also support other translations that a set of form choices may not represent:

When moving data into Enrollment…	Predefined List	Integration Mapping List
Handle an incoming value with no listed match	No fallback behavior is defined.	Keep the incoming value, replace it with a set value, or leave it blank.
Translate an empty incoming value to a value such as `Unknown`	A form choice cannot have an empty Display value.	An empty If value is can map to a non-empty Replace with value.
Replace an incoming value with blank	A form choice cannot have an empty Stored value.	Replace with can be empty.
Map several incoming codes to the same form value, such as `Other`	Stored values must be unique.	Multiple If value is values can map to the same Replace with value.

Use a Predefined List to define form choices and their associated values. Use an Integration Mapping List when imported data needs rules for both listed values and values that do not match.

Rules for a valid list

For a list to be valid:

It must have a name and at least one value pair.
The name is limited to 100 characters and must be unique within the Solution, regardless of capitalization.
If value is entries must be unique regardless of capitalization. Replace with values can repeat.
Either side of a pair can be empty. A row with both sides empty is ignored when the list is saved.