Field Mapping and Value Transformation in Data Import Process | Enrollment

A Field Mapping pairs a source property with a target form field. Each mapping moves one value from the source into one field on the form.

In the mapping list:

The target form field appears on the left.
The source property appears on the right.
A mapping can optionally include a Transform Rule, but they are not shown in the mapping list.

Field Mappings are processed in the order they are listed.

Add a Basic Field Mapping

Use a Basic Mapping when a form field is populated from a single source property.

To add a Basic Mapping:

Open the Source Record or Subrecord.
Add a Field Mapping.
Select the target form field.
Select the source property.
Save the mapping.

Source properties are displayed using the format:

TableName.ColumnName

The system imports the source value into the selected form field.

Duplicate a Field Mapping

When a Field Mapping is duplicated:

The source configuration is copied.
Any configured Transform Rule is copied.
The target form field is cleared.

The target form field must be reassigned before the mapping is saved.

Reorder a Field Mapping

Field Mappings can be reordered by dragging them within the list.

The displayed order determines the order in which mappings are processed.

Add an Advanced Mapping

Use an Advanced Mapping when a single source property cannot provide the required value.

Instead of selecting one source property, enter an expression in the Value to import field.

An expression can contain:

Source properties
Literal text
Multiple source properties combined

Typing / in the Value to import field opens the source-property picker.

Selected properties are inserted into the expression.

Example

An administrator can combine a first name and last name into a single form field.

FirstName + " " + LastName

Advanced Mapping can also be used to assemble values from multiple source properties.

Format Values

A Transform Rule modifies a mapped value before it is written to the target form field.

Each Field Mapping supports one Transform Rule.

To apply a Transform Rule:

Open the Field Mapping.
Select Apply transformations.
Select a transformation type.
Configure the transformation.
Save the Field Mapping.

Available Transformations

Transformation	Description
Polish	Applies a formatting rule from a predefined library. Polish formatting supports: Text Names Dates Times Phone numbers Addresses Use Polish to normalize a value into a standard format.
Regex	Extracts part of a value using a regular expression pattern. Use Regex when a source value contains additional text that should not be imported.
Replace	Replace performs a literal find-and-replace operation. Use Replace to convert known source values into different values.
Split	Split returns a specific segment of a delimited value. Use Split when a source property contains multiple values in one string.
Trim	Trim removes leading and trailing characters. Use Trim to clean up spaces and other unwanted padding.
Integration Mapping List	Converts a source value using a reusable list of mappings.
Script	Applies a Function Library function to the value.

Script

A Script is a transformation-like function library that may appear in a Field Mapping when an existing configuration is migrated to the new Data Sources configuration.

During JIT migration, if part of a legacy configuration cannot be converted to a supported transformation, the migration process uses Script to preserve the existing behavior rather than changing the configuration unexpectedly.

Script transformations are created as part of the migration process and are not customer-manageable. You cannot create a new Script transformation, change the associated function, or edit the script.

If the function associated with a Script transformation is no longer available, the Field Mapping displays the following message: “The selected script function is no longer available.”

Check for Setup Issues

Data Source configurations use two layers of validation.

Field-Level Validation

Field-level validation occurs when a dialog is saved.

Examples include:

Missing required values
Invalid selections
Incomplete configuration

Errors appear directly in the dialog so they can be corrected before saving.

Holistic Validation

Holistic validation runs:

After save operations
After delete operations
After Metadata Sync completes

Holistic validation evaluates the entire configuration and identifies issues that cannot be detected from a single dialog.

Examples include:

Missing source properties
Removed target form fields
Invalid Integration Mapping Lists
Missing Script functions

Validation Indicators

Validation issues appear throughout the configuration tree.

Location	Indicator
Source Record	Error badge showing issues within the Source Record and its children
Subrecord	Error badge showing issues within the Subrecord
Field Mapping	Error badge showing issues on that mapping

Selecting the affected item displays additional error details.

Show Only Invalid Mappings

Use the Only show invalid mappings toggle to display only mappings and subrecords that contain validation issues.

When the toggle is enabled:

Only invalid mappings and subrecords are displayed.
Source Records remain visible.
Drag-and-drop reordering is disabled.

If no validation issues exist, the page displays:

All field mappings are valid.

Sync & Validate

PowerSchool SIS Data Sources support Metadata Sync.

The Sync & Validate button:

Retrieves schema information from PowerSchool SIS.
Updates cached metadata.
Runs holistic validation.

While the operation runs:

A loading spinner is displayed.
The button label changes to:

Syncing & Validating...

A Last Synced timestamp shows when metadata was most recently retrieved.

Use Sync & Validate When

Extension Tables have changed.
The SIS Connection has changed.
Source fields are missing from mapping dialogs.
Validation errors appear to reference outdated schema information.

An inline Sync button is also available next to Extension Table selectors.