Data Export Manager
On this page:
Using the Data Export Manager, you can quickly and easily export data from PowerSchool tables, database extensions, and PowerSchool data sets into a text file.
Individual access to most PowerSchool tables is provided through Data Export Manager. Some tables have been removed for security reasons or because they are part of system processes.
Database extensions allow you to display customized information in PowerSchool. Access to one-to-one, one-to-many, and independent database extensions is provide through Data Export Manager. Database extensions may be created through the PowerSchool user interface and define the table structure and related fields.
- Database extension tables are listed in the Export From pop-up menu on the Data Export Manager page using the name of the table.
- Database extension table fields are available in the Data Export Manager when selecting fields to export.
- After choosing a database extension table, the database extension table fields appear in a field list on the left side of the Data Export Manager page. The fields appear in the following order:
- Each table lists its fields alphabetically after any primary and foreign keys.
- If the selected database extension table is a 1-to-1 or a 1-to-many extension of a core table, the extension fields appear first, followed by the associated parent table and any of its extensions.
- If the database extension table is an independent table that does not have a parent table, its fields appear first, followed by any of its extension fields.
- A child table extension will list its fields and extensions first, followed by its parent table fields and extensions.
- Standard export options are available when exporting from a database extension table.
- Export results for an export from a database extension table are displayed in the downloaded export file.
For more information, see Database Extensions.
PowerSchool Data Sets
A PowerSchool data set is a data source that can be accessed via Data Export Manager, as well as the API. A typical PowerSchool data set declares a set of arguments, a set of columns, and a select statement. The arguments are optional, but the columns and select statement are required. A PowerSchool data set is pre-defined by PowerSchool and includes export modules for Course Archive, Incident, Student Email, Transportation, as well as data sets for Students + Courses and others.
Additional Data Sets
Additional data sets, also available through Data Export Manager, provide more specific access to data within PowerSchool and are not supported by PowerSchool and provided for convenience only. Additional data sets may be defined by PowerSchool or by a third-party as a PowerQuery, and installed in PowerSchool via the Plugin Package. Once the plugin is installed and enabled, the third-party data set becomes accessible as another resource in PowerSchool.
- PowerQueries under the additional data sets section are typically created for a specific function within PowerSchool. In most cases the PowerQueries that are PowerSchool provided are used on specific pages in the SIS UI. As these are typically designed for use within a core PowerSchool page they may not necessarily be designed for use with the Data Export Manager. Consequently, unexpected behaviors may occur when used outside of their primary context.
- PowerQueries may return fields that are calculated and do not exist as a field in the database. For example, the absence or existence of a record in another table or a calculated value.
- PowerQueries may show in light gray (disabled) and not be selectable if the current logged in user does not have appropriate Field Level Security access to all fields the PowerQuery may return. This includes Database Extension fields that Data Export Manager may make available automatically.
The participant name fields are designed to export only people who have been created during the incident itself. This field will remain blank for existing students and staff. Participant_Student_Number and/or Participant_Teacher_Number would be the recommended column selection for existing users if this information is needed.
For example, if a person from outside the district is caught on campus smoking with a senior by a staff member. When writing the incident you would enter the student and staff as normal, but since the person from outside is not in the system but still an offender; they would be created using the option for Create Other. That information there would be what would be placed in the participant fields.