CSV and TAB Data Targets deliver approved submission data as files instead of sending records to an SIS API. A CSV Data Target produces a comma-separated file. A TAB Data Target produces a tab-delimited file.
File delivery uses Target Records to define the output files and Field Mappings to define the values written to each output column. Unlike PowerSchool SIS and eSchoolPlus Data Targets, file Data Targets do not require an SIS Connection, do not use SIS metadata, and do not automatically create a Student Target Record.
Creating a CSV or TAB Data Target
-
From the Data Targets list, select Create data target.
-
Select CSV or TAB as the Target type.
-
Enter a Target name and select a Data view.
-
Configure the applicable General settings.
-
Select Save.
-
On the Data Target detail page, add a file Target Record, configure its file settings and column headers, then add the Field Mappings that populate the output columns.
CSV and TAB Data Targets display only the Data Target settings that apply to file delivery. They do not display SIS Connection, Student, Contacts, or Documents settings.
CSV and TAB Target Records
Add a CSV File Target Record to a CSV Data Target or a TAB File Target Record to a TAB Data Target. Each Target Record defines one delivered file.
-
Name identifies the Target Record in Data Targets.
-
Dataset label controls the label shown for the record during delivery review. It can include Field Mapping references.
-
Default to expanded controls whether the record's mappings are expanded by default in delivery review.
-
File name is required. Enter the base file name only. The system adds the .csv or .tab extension that matches the Target type.
-
Include header row controls whether the delivered file includes the configured column-header row.
-
Preserve line breaks is available for CSV Target Records and preserves line breaks in mapped output values.
-
Insert row conditions define the conditions that determine whether a row is included in the delivered file.
File names can contain letters, numbers, spaces, hyphens, underscores, and periods. The system removes a typed file extension and appends the appropriate .csv or .tab extension when it saves the Target Record.
Defining Output Columns
Each CSV or TAB Target Record has an ordered list of Delivery file column headers. Define the column headers before configuring Field Mappings because the headers are the available mapping targets.
Add column headers individually, edit their names, drag them to change their order, or remove them. Column-header values must be unique. The configured order is the output-column order in the delivered file.
To define headers from an existing file layout, select Upload sample file and upload a sample CSV or TAB file that contains the expected header row. The uploaded file must match the Target Record's format. The system reads the header row only and does not store sample data. When headers already exist, choose whether to replace all current headers or add only headers that do not already exist.
When a header is removed, the system identifies exported Field Mappings that use that header. Saving the Target Record removes those affected Field Mappings after confirmation. Update or remove dependent mappings before changing a column-header layout when their output values must be retained.
File Delivery Behavior
During delivery, the Data Target uses its Data view to select submission records. For each file Target Record, the system evaluates the Insert row conditions and writes a row only when the configured conditions are met.
Each exported Field Mapping supplies the value for its selected column header. The system writes columns in the configured header order. Mappings that are not included in exported data do not create output columns, even when they are available for use as intermediate mappings or expressions.
The file name, file format, header-row setting, column-header order, row conditions, and Field Mappings together determine the delivered CSV or TAB file.