Open topic with navigation

Adding Extension and Child schemas

An Extension schema has a one-to-one relationship with its associated Main schema [>>]. A District Administrator can add a custom Extension schema to a Main schema and to custom Child schemas; however, he or she cannot delete a custom Extension schema if it is referenced by a page in another schema in the database, nor can he or she change a built-in Extension schema, or add one custom Extension schema to another.

A Child schema has a one-to-many relationship to the Main schema. Fields in a Child schema appear as a grid on the page. The administrator can add a Child schema to a main schema and to another custom Child schema, but cannot add a Child schema to an Extension schema, change a built-in Child schema, edit or delete a Child schema that is locked [>>], or change a Child schema that is referenced by a page in another schema.

To add an Extension or Child schema [You can do this if your role is District Administrator.DA]:

1

In the Admin menu, click District Setup. District Setup page appears.

2

Under cTools, click Manage Schemas. The cTools Manage Schemas page appears.

3

Click the feature area [>>] that contains the schema to be extended.

=

Student Health Tracking schemas originate from within the Student Demographic feature area. Therefore, to work with Health schemas, click the Student Demographic feature area.

4

On the Manage Schema Properties page, under Schema name, select the schema to be extended.

5

In the Actions menu, click Add Schema > Add Child or Add Extension.

=

To edit a schema, click it. It is possible to edit unlocked schemas [>>] created by others.

=

To delete a schema, select it and in the Actions menu click Delete Schema.

6

On the Add/Edit Child or Add/Edit Extension page, enter or change information, which includes:

=

Schema Name: The name of the custom schema. The name must be unique and have no spaces or underscores.

=

Database table name: CDM_: The name of the table in the custom schema. The name of a custom table in PowerSchool SMS is always prefixed by "CDM". The name cannot have spaces, use underscores instead.

=

Display name: The schema name as it appears on pages and in bread crumbs.

=

Description: Additional information about the schema.

=

Default display field: The field selected here is used to construct part of the audit message [>>] that appears when a change is made to any field in this custom schema. Note: No fields appear here until they are added to the schema [see Configuring fields in a schema >>].

=

Default search field: The field users search on by default when searching on a custom schema (Extension schemas only) [>>]. The field you designate as the default search field should be the field that best describes the type of records in the schema. Specifying a default search field is optional; however, if a field is not specified as a default search field, the operators "includes" and "excludes" are not available in the search control. Note: No fields are available in this drop-down list until they are added to the schema [see Configuring fields in a schema >>].

=

Copy to planning calendar: This option appears if the data in the Main schema [>>] can be different between the active and planning calendars. The setting for this option controls what happens to the data in the schema during Year-End Processing [>>]. If this option is selected, the data in this schema is copied from the active to the planning calendar during Year-End Processing; if not selected, data in this schema is deleted. The setting for this option defaults from the Main schema; however, the setting can be changed. Alternatively, individual fields can be set so that their data is not copied [see Setting calendar options for a custom field >>].

=

Keep in active calendar at year-end: This options appears if the data in the Main schema [>>] is the same in both the active and planning calendars. If this option is selected, the data in this schema remains in the active calendar during Year-End Processing; if not selected, data in this schema is deleted. The setting for this option defaults from the Main schema; however, the setting can be changed. Alternatively, individual fields can be set so that their data remains in the active calendar at year end [see Setting calendar options for a custom field >>].

=

Enable auditing: This setting controls whether the data in a custom schema is audited. The setting defaults from the Main schema; however, this setting can be changed on the Enable Auditing page [see Configuring fields in a schema >>].

7

Click Save.

8

Click Apply Pending Changes.

www.powerschool.com
Tel: 866-434-6276
Email: smssupport@powerschool.com

Copyright 2015-2016 PowerSchool Group LLC and/or its affiliate(s). All rights reserved. All trademarks are either owned or licensed by PowerSchool Group LLC and/or its affiliates.