Data Targets | PowerSchool SIS and CCLR

Self-Service Data Targets is the customer admin portal experience for configuring how approved form submission data is delivered to a district destination. It gives eligible District Admins a single place to create, view, edit, validate, and remove delivery configurations for a form.

Each Data Target defines the destination type, the records to deliver, the Field Mappings that supply delivered values, and the settings that control matching and delivery behavior. A Data Target can deliver data to a PowerSchool Student Information System (SIS), an eSchoolPlus SIS, or a file in CSV or TAB format.

The experience keeps the configuration specific to the selected target type. Users see only the settings, Target Records, fields, and validation rules that apply to the destination they are configuring.

Intended Audience

District Admins with the Configuration role can configure, review, support, or troubleshoot customer delivery configurations. It explains the current Data Targets experience in the customer admin portal, including the configuration decisions that affect what data is delivered and how delivery errors are resolved.

Supported Target Types

Target Type	Delivery Destination	Configuration Focus
PowerSchool SIS	A PowerSchool SIS instance accessed through its API	SIS connection, target records, SIS fields, matching behavior, and delivery options.
eSchoolPlus	An eSchoolPlus SIS instance accessed through its API	SIS connection, target records, eSchoolPlus fields, matching behavior, and delivery options.
CSV	A comma-separated values file	File output records, column headers, field mappings, and output values.
TAB	A tab-delimited file	File output records, column headers, field mappings, and output values.

The selected Target Type cannot be changed after the Data Target is created. To use a different Target Type, create a separate Data Target.

Feature Boundaries

Self-Service Data Targets configures supported delivery targets in the customer admin portal. Delivery types other than PowerSchool SIS, eSchoolPlus, CSV, and TAB are not available in this experience. Existing unsupported target types are not managed from the customer admin portal and continue to be managed through the appropriate internal tools.

Existing PowerSchool SIS, eSchoolPlus, CSV, and TAB Data Targets appear in this experience without manual migration.

Data Targets can designate an existing Year-Round Update (YRU) configuration as a YRU delivery target when the required prerequisites are present.

Access and Prerequisites

Customer Availability

Data Targets is available for a customer only when the Customer Data Delivery Configuration feature flag is enabled for that customer and the customer has Form Building enabled. Availability is evaluated for the customer account being accessed. A user who can access one customer's Data Targets cannot view or modify another customer's delivery configuration unless they access that customer separately.

The customer admin portal displays only the Data Target types supported in this experience: PowerSchool SIS, eSchoolPlus, CSV, and TAB. Unsupported delivery types are not available from the Data Targets list or through a direct detail-page URL.

Roles and Access

District Admins need the Configuration role to access Data Targets. No separate Data Targets permission is required.

They can access Data Targets while working in a customer account when Data Targets are available for that customer. The customer’s Form Building availability and Data Targets feature flag still controls whether the area is visible.

Users who do not meet the access requirements do not see Data Targets in the customer admin portal. Direct navigation to a Data Targets page is blocked.

Open Configure Workspace Tools for the form, either from the ellipsis (three dots) menu on the Student Data page or the gear icon within the workspace of a given form. Select the Data Targets tab.

Required Configuration Before Creating a Data Target

Create Data Targets from the form that supplies the submission records to deliver. Before creating a Data Target, confirm that the form and its supporting configuration are available for the workspace.

For PowerSchool SIS and eSchoolPlus Data Targets, an SIS Connection for the selected target type must be available. The SIS Connection identifies the district system that receives delivered data. The Data Target creation workflow filters the connection list to the selected target type.

A Data view is required unless the Data Target is designated for YRU Delivery. The Data view determines which submission records are included when standard delivery runs. YRU delivery does not use a Data view because YRU controls record selection through its own workflow. See YRU Delivery Target Assignment.

A form can have more than one Data Target, and each Data Target has its own configuration.

Core Concepts

Data Target Hierarchy

A Data Target belongs to one form. A form can have multiple Data Targets when the same submission records must be delivered to more than one destination or in more than one format.

Level	Definition
Data Target	The top-level delivery configuration. It stores the Target Type, connection or file settings, Data view, and settings that apply across the target.
Target Record	A record-specific configuration within a Data Target. A Target Record identifies the destination entity or output record that receives data, such as a Student, Contact, an extension, or a file row.
Field Mapping	A rule within a Target Record that supplies a value to a Target Field.
Subrecord	A nested, repeatable group of Field Mappings within a Target Record. For example, a Contact Target Record can contain Address, Phone, and Email subrecords.

During delivery, the Data Target selects the submission records to process, Target Records define the destination records or rows, and Field Mappings supply the values for each destination. The selected Target Type determines the available Target Records, Target Fields, and target-specific settings.

Data Target Lifecycle

Create a Data Target for a form and select its Target Type.

Configure the Data Target settings that apply to the selected destination.

Add and configure Target Records. For target types with required records, the system creates the required Target Record and its default Field Mappings automatically.

Configure Field Mappings, subrecords, transformations, and delivery options for each Target Record.

Synchronize destination metadata where the target type supports metadata discovery, then validate the complete configuration.

Resolve validation messages and repeat validation until the Data Target is ready to deliver.

Deliver approved submission data using the Data Target's configured selection, records, mappings, and delivery settings.

Users can return to a Data Target to refine its configuration. Changes take effect for future delivery processing after they are saved.

Shared Configuration Terms

Term	Definition
SIS Connection	The configured API connection used to communicate with a district's PowerSchool SIS or eSchoolPlus SIS instance.
Data view	The saved view that selects which submission records are included when a Data Target delivers data.
YRU	Year-Round Update, an in-year workflow that lets families update specified student and contact information. YRU Delivery designates the Data Target used to deliver those updates to the linked SIS.
Source Expression	The value-producing side of a Field Mapping. A Source Expression can use a form field, system property, date or time token, another mapping, or an expression.
Target Field	The destination SIS field or file column that receives a mapped value.
Intermediate Mapping	A named temporary mapping that calculates a value for use by other Field Mappings in the same Target Record.
Metadata Sync	The process that retrieves destination metadata so the configuration experience can present current destination tables, fields, or extensions where supported. Only applies to PowerSchool SIS, not eSchoolPlus or file,
Include in delivery view	A Field Mapping option that controls whether the mapped value appears during delivery review.
Include in exported data	A Field Mapping option that controls whether the mapped value is included in the delivery output.
Copy back to submission record	A Field Mapping option that writes the mapped value back to its source form field on the submission record.
Target Record Field Mappings	References to other mappings in the same Target Record, displayed with the map: prefix and custom label when one is defined.

Managing Data Targets

Data Targets List

The Data Targets list displays the Data Targets configured for the current form. Each row includes:

Data target name
Type
SIS connection and SIS URL for SIS API targets
Data view
Validation status

Select a Data Target name or row to open its detail page. Use the action menu to select Edit or Delete.

Validation status helps identify configurations that need attention:

Valid indicates that validation is completed without errors.
Not validated indicates that validation is not completed for the Data Target.
A validation issue count indicates the number of current validation errors.

CSV and TAB Data Targets do not use an SIS Connection, so the list displays a dash in the SIS Connection and SIS URL columns for those target types.

Creating a Data Target

From the Data Targets list, select Create data target.
In Target details, select a Target type and enter a Target name.
For PowerSchool SIS and eSchoolPlus, select the required SIS Connection. The list contains connections that match the selected Target type.
Select a Data view to define the submission records included in delivery. When configuring a YRU delivery target, use the YRU Delivery workflow described in YRU Delivery Target Assignment.
Configure the settings displayed for the selected Target type. The system applies target-type-specific defaults when the Target type is selected.
Select Save.

The system creates the Data Target and opens its detail page. Configure Target Records and Field Mappings from the detail page. Where a target type requires a Student Target Record, the system creates that record and its default Field Mappings automatically.

Editing a Data Target

Open a Data Target and select Edit to open its settings drawer. Target type is read-only after creation. The Target name, connection, Data view, and applicable target-type settings remain editable.

Select Save to apply changes. The settings drawer displays only the configuration sections that apply to the selected Target type.

Deleting a Data Target

Use the Data Target action menu to select Delete, then confirm the prompt. Deleting a Data Target permanently removes the Data Target and its Target Records, Field Mappings, subrecords, and settings. This action cannot be undone.

Shared Data Target Settings

The settings drawer organizes configuration into sections. Target details contains the Target type, Target name, SIS Connection when applicable, YRU Delivery when available, and Data view. General contains settings shared by the selected target type, including Allow unapproved records.

PowerSchool SIS Data Targets and eSchoolPlus Data Targets also display target-specific Student, Contacts, and Documents sections. CSV and TAB Data Targets display only the sections that apply to file delivery. See the target-type subchapters for the available settings and their delivery effects.

Target Records and Field Mappings

Adding a Target Record

Open the Data Target detail page.
In the Target records panel, select Add.
Select a Record type. The available choices depend on the Data Target's Target type.
Enter a Name.
Configure the settings displayed for the selected Record type.
Select Save.

The new Target Record appears in the Target records panel and becomes available for Field Mapping configuration. The system applies default Field Mappings and subrecords where they apply. Target-type-specific rules, such as required Student Target Records, are described in the relevant target-type subchapter.

Editing Target Record Settings

Select a Target Record, then use its action menu to select Edit. The edit drawer shows the Record type as read-only and displays the settings that apply to that Target Record.

Common settings include:

Name
Dataset label, which can include references to Field Mappings in the Target Record
Default to expanded, which controls whether the Target Record is expanded by default during delivery review

Additional settings depend on the Target type and Record type. Examples include PowerSchool SIS extension selection and matching, eSchoolPlus subrecord behavior, and CSV or TAB file settings. Configure those settings in the target-type-specific chapters of this guide.

Default, Required, and Must-Exist Field Mappings

PowerSchool SIS and eSchoolPlus use default Field Mappings to give new Target Records a usable starting configuration. The system creates the default destination mappings for the selected Target Record, and the District Admin selects or updates the source values to match the district's form and delivery requirements. When a Target Record stores mappings only in subrecords, the system also creates its first populated subrecord.

A default Field Mapping is editable and can be deleted unless it has a required or must-exist constraint. These constraints protect the destination mappings needed for valid delivery:

Mapping Type	Meaning	What the Configuration Does Not Allow
Required	The Field Mapping must remain in the Target Record and must contain a source or expression that supplies a value for delivery.	Deleting the mapping, clearing or changing its Target Field, using it as an intermediate mapping, turning off Include in exported data, or saving the mapping without the required source or expression.
Must-exist	The Field Mapping must remain in the Target Record as a destination mapping. It does not require a source or expression value.	Deleting the mapping, clearing or changing its Target Field, using it as an intermediate mapping, or turning off Include in exported data.

The Field Mapping drawer identifies required values with a Required badge. Required and must-exist mappings keep the Target field locked to the correct SIS field. The protected mappings depend on the Target Record type and, in some cases, the selected Data Target settings.

Reordering Target Records

Drag a Target Record by its handle to change its position in the Target records panel. The order determines the delivery processing sequence: Target Records higher in the list are processed first.

Place records that establish data required by other records before their dependents. For example, place a Student Target Record before Contact, extension, or other student-dependent Target Records. The system saves the new order when the record is dropped.

Deleting a Target Record

Use the Target Record action menu to select Delete, then confirm the deletion. Deleting a Target Record permanently removes that Target Record, its Field Mappings, and its subrecords.

Required Target Records cannot be deleted. For example, the required Student Target Record in a PowerSchool SIS or eSchoolPlus Data Target remains in the Data Target.

Field Mapping Grid

Select a Target Record to view its Field Mappings. Each mapping row shows the destination Target or Intermediate mapping name on the left and the source or calculated value on the right.

The right side of the row reflects the Mapping type:

Basic mappings show the selected Source.
Advanced mappings show the configured Value to send.
Conditional mappings show the values sent when the condition is true and false.

The grid also shows any custom label and flags for In delivery view, In exported data, and Copy to submission record. A mapping with unresolved errors displays an error summary. Use Only show invalid mappings to focus the grid on mappings that need attention.

For Target Records with subrecords, the grid groups mappings beneath subrecord headers such as Address 1, Phone 1, or Race 1. Use the Target Record, subrecord, or Field Mapping action menu to perform the available actions for that item.

Adding and Editing a Field Mapping

Select the Target Record that will contain the Field Mapping.
Select Add and choose Field mapping or the applicable subrecord type. To add a mapping to an existing subrecord, select Add mapping from that subrecord.
Select the Mapping type: Basic, Advanced, or Conditional.
Select the Target field, or enable Intermediate mapping and enter an intermediate mapping name.
Configure the source, value, or condition required by the selected Mapping type.
Configure transformations and delivery options when needed.
Select Save.

To edit a mapping, select its row or choose Edit from its action menu. The drawer opens with the current mapping values. Available Target Fields depend on the selected Data Target and Target Record: SIS fields for PowerSchool SIS and eSchoolPlus, or configured column headers for CSV and TAB.

The system prevents duplicate Target Fields within the same Target Record or subrecord. It also prevents duplicate intermediate mapping names and prevents an intermediate mapping name from matching an existing Target Field.

Mapping Types

Mapping Type	Behavior
Basic	Sends a value from one selected source to one Target Field. Select the Target field, then select the source that provides the delivered value. A Custom label is optional and controls the human-readable label shown during delivery review. Use Basic mappings for direct form-field, property, token, or mapping-reference delivery. A required mapping must include a source. Other Basic mappings can remain unconfigured until the District Admin selects the appropriate source.
Advanced	Sends a value expression to one Target Field. Use Value to send to enter text, combine multiple values, or insert supported tokens with the slash-command picker. Use Advanced mappings when the delivered value cannot be supplied by a single Basic source. The expression can combine form fields, properties, date and time tokens, and references to other Field Mappings. A Custom label remains available for delivery review.
Conditional	Evaluates configured conditions and sends a different value depending on the result. Add the conditions, then configure Value to send if condition is TRUE and Value to send if condition is FALSE using text or slash-command tokens. At least one conditional value is required. When both values are supplied, they must differ. Required mappings must include a value for both outcomes. Use a Conditional mapping when the destination value depends on submission data or another mapping result.
Intermediate	Calculates a value for use by other Field Mappings in the same Target Record instead of sending the value directly to a Target Field. Enter a unique Intermediate mapping name, then reference it from another mapping through Target Record Field Mappings. Intermediate mappings are not included in exported data and cannot copy values back to the submission record. Required and must-exist mappings cannot be converted to intermediate mappings. Update any mappings that reference an intermediate mapping before deleting or renaming it.

Mapping Sources

The source selector and slash-command picker group available values into these categories:

Source Group	Use	Example
Form Fields	Values collected by the form associated with the Data Target's form. Fields display their field ID and configured label when available.	stu_FirstName (Student First Name)
System Properties	Submission-level values displayed with the prop: prefix.	prop:ActionSubmissionID (Action Submission ID)
Dynamic Date/Time Properties	System date and time values available at delivery time.	prop:CURRENT_DATE (Current Date)
Target Record Field Mappings	References to other mappings in the same Target Record, displayed with the map: prefix and custom label when one is defined.	map:Students.First_Name or map:Students.First_Name (custom label)

Basic mappings select one source. Advanced and Conditional mappings use the slash-command picker to insert one or more source tokens into a value expression.

Subrecord Mappings

Subrecords are nested, repeatable mapping groups within a Target Record. Each subrecord has its own Field Mappings and appears with a one-based index, such as Address 1, Address 2, Phone 1, or Race 1. The index updates when subrecords are added, deleted, or reordered.

Add a mapping from the subrecord header to ensure it is associated with that subrecord. The selected Target is unique within each subrecord instance, so the same Target Field can be used in a different instance of the same subrecord type when the delivery design requires it.

Deleting a Field Mapping

Select Delete from the Field Mapping action menu and confirm the deletion. Deleting a mapping removes it from the Target Record or subrecord.

Required and must-exist mappings cannot be deleted. Before deleting an intermediate mapping, update or remove any other mappings that reference it so the Target Record does not contain a missing mapping reference.

Transformations

Use Apply Transformations in the Field Mapping drawer to modify a mapping value before delivery. Each Field Mapping supports one transformation, and transformations cannot be combined. The available transformation types are Mapping list, Polish, Pad, Replace, Regex, Split, and Trim.

Transformation	Purpose
Mapping list	Select a predefined list to translate source values into the values required by the destination. For example, a Mapping list can translate a collected response into a corresponding destination code. If no list item matches, the original value is retained.
Polish	Select a Polish rule from the available rule groups, then configure Options when the selected rule requires them. Available rules include transformations such as Proper Case, Phone Digits Only, and Date ISO.
Pad	Select whether to add characters to the Start or End of the value, enter a positive Target length, and optionally enter the Pad character. For example, padding `123` to seven characters with `0` at the start produces `0000123`. Values that already meet or exceed the target length remain unchanged.
Replace	Enter the literal Text to replace and the Replace with value. For example, replace `Assoc.` with `Association`. All occurrences of the specified text are replaced.
Regex	Enter a Regular expression to return the first matching portion of the mapped value. For example, applying `\d+` to `(555) 123-4567` returns `555`. Regex does not replace or validate the value, and it returns a blank value when no match is found.
Split	Enter one or more Delimiter values and the one-based Index of value to retain. For example, splitting `LastName, FirstName` at `,` and retaining index `2` returns `FirstName`. A missing delimiter or out-of-range index returns a blank value.
Trim	Select Both, Start, or End, then optionally enter the Character to trim. For example, trimming both ends of `123 Main St` without specifying a character removes the surrounding whitespace.

Delivery Options

Delivery Review presents the delivery output by Target Record and field value. The Field Mapping drawer includes options that separately control what appears in Delivery Review, what is sent to the destination, and what is written back to the submission record.

Option	Behavior
Include in delivery view	Displays the calculated mapped value in Delivery Review. This option does not control whether the value is delivered.
Include in exported data	Includes the mapped value in the delivered SIS record or output file. When this option is cleared, the value is not sent to the destination.
Copy back to submission record	Writes the mapped value back to its source form field on the submission record.

Copy back to submission record is available only for a Basic mapping that directly references one form field. The same form-field source can have this option enabled in only one Field Mapping across the Data Target.

Intermediate mappings can appear in Delivery Review, but they are not included in exported data and cannot copy values back to the submission record. For required mappings, Include in exported data remains selected and cannot be changed. Must-exist mappings do not have this restriction.

Clearing Values in the SIS

Advanced and Conditional mappings provide the Delete value in SIS controls for clearing an existing destination value during delivery.

For Advanced mapping, enable Delete value in SIS to clear the destination value instead of sending a value expression. For a Conditional mapping, enable Delete value in SIS if condition is TRUE or Delete value in SIS if condition is FALSE to clear the destination value for that outcome. The enabled toggle replaces the corresponding value input.

Use this option only when the delivery configuration is intended to remove an existing SIS value. Basic mappings do not provide the clear-value option.

Validation

Validation checks the Data Target configuration for conditions that can prevent successful delivery or produce unintended results. It identifies missing required mappings, invalid Target Fields, duplicate mappings, broken references, circular dependencies, and target-type-specific configuration issues.

Trigger	Validation Scope
Saving a Field Mapping	The Field Mapping and its Target Record, including required values, duplicate Targets, and mapping references.
Saving a Target Record	Target Record settings, applicable required fields, and target-type-specific configuration.
Saving a Data Target	Data Target settings and any targeted validation required by the changed setting.
Selecting Sync & Validate	All Target Records, Field Mappings, and target-level configuration. PowerSchool SIS also refreshes destination metadata.
Publishing the form	Data Targets associated with the form.

Use Sync & Validate after changing mappings, Target Records, destination metadata, or target-wide settings. It is the full configuration check for the Data Target.

For PowerSchool SIS, Sync & Validate includes schema synchronization. For eSchoolPlus, CSV, and TAB, it runs validation without a PowerSchool SIS metadata sync.

Validation Results

Validation results appear in the places where the configuration can be corrected:

The Data Targets list shows Valid, Not validated, or a validation issue count for each Data Target.
The Data Target detail page shows target-level errors that affect the overall configuration.
The Target records panel displays an error count for each Target Record.
The selected Target Record displays error summaries and inline messages for settings such as Record type, Name, and extension table selection.
Field Mappings and subrecords display their own error summaries and inline messages.

Select a Target Record with an error count to review its configuration. Use Only show invalid mappings in the Field Mappings panel to isolate mappings with unresolved errors.

Common Configuration Errors

Error	Cause	Resolution
A field mapping already exists with this Target selection.	Two mappings in the same Target Record use the same Target Field.	Change or remove one of the mappings.
A field mapping already exists with this Target selection in this {type} record.	Two mappings in the same subrecord instance use the same Target Field.	Change or remove one of the mappings in that subrecord.
A field mapping already exists with this Intermediate mapping name.	Two intermediate mappings use the same name.	Rename one of the intermediate mappings.
The Source references map:{name}, which does not exist in this target record.	A mapping references an intermediate mapping that does not exist.	Correct the mapping reference or create the missing intermediate mapping.
Schema item {name} is part of a circular reference chain.	Mappings reference each other in a loop.	Change one or more references to break the loop.
Form field {fieldId} no longer exists in the published form.	A mapping or file-row condition references a deleted form field.	Select a current form field or remove the reference.
The Target references a SIS field that does not exist.	A mapping references a removed or unavailable SIS extension field.	Refresh metadata, then select a valid Target Field.

The wording of target-type-specific required-field errors identifies the affected Target Record and missing Target Fields. Configure or restore the required mappings, then run Sync & Validate again.

YRU Delivery Target Assignment

Use YRU Delivery to designate a PowerSchool SIS or eSchoolPlus Data Target for an existing Year-Round Update configuration. The option is available only when the associated form is Private, YRU is enabled on the form, and a YRU configuration is linked to the form.

Configuring a YRU Delivery Target

Create or edit an eligible PowerSchool SIS or eSchoolPlus Data Target.
In Target details, select YRU Delivery.
Save the Data Target.

YRU determines the records to process through its own workflow, so the Data view selector is disabled when YRU Delivery is selected. A form can have only one YRU delivery target. Other Data Targets on the same form continue to use their own Data views.

YRU Product Configuration Boundary

Data Targets assigns a delivery target to an existing YRU configuration. It does not create, enable, or otherwise configure the YRU product. Complete the YRU product configuration before designating the Data Target for YRU delivery.