PowerSchool University2014

Custom Field Migration

Trainer NameTrainer/Consultant

Agenda Custom Fields A Little History

Legacy Custom Field Data Migration

Migrating User Custom Fields

Changes After Migration

2

Custom Fields - A Little History

3

Legacy Custom fields are created inside a Character Large Object (CLOB). When data is stored this way it:

Is harder to access

Cannot be obtained through direct SQL

Impacts performance

In addition, legacy custom fields had other issues:

Datatypes not defined

One-to-many records not supported

Legacy Custom Fields

4

Database Extensions Benefits

5

Supports one-to-one one-to-many and standalone tables

Allows fields to have defined datatypes

Can be based on most existing tables

Allows direct access to tables and fields from SQL

Improves performance

Includes enhanced customization features

Legacy Custom Field Data Migration

6

Types of Legacy Custom Fields

7

Migration Process State Reporting

8

State and Province migrations will be on state- and province-specific schedules.

Migration Process Activities

9

Activities are migrated during the PowerSchool 7.10 update to a new table called Activities.

Migration Process PowerSchool Core

10

Two Sets: Core Fields and Core Fields2

Might also have State Compliance Fields

One time, irreversible process

Migration Report and Get Data are critical to avoid data loss

Migration Process User-Created Fields

11

User-created custom fields can be moved manually when new fields are created

There is also a process to mass move user-created custom fields

PowerSchool Core Custom FieldData Migration

Select the Custom Field set, run the Migration Report, and get the data (if needed)

Back up your data and migrate the custom fields

Look at the Migration History

12

Review the Migration Summary

13

Select the custom field set, run the Migration Report, and get the data (if needed).

14

Back up your data and migrate custom fields.

15

Review the Migration Summary.

16

Look at the Migration History.

Now Its Your Turn

Complete Demonstration activity 1:

Migration of PowerSchool Core Fields Process

17

User Custom Fields Migration

18

Three options One field at a time: Basic Mode

One field at a time: Advanced Mode

All fields at once: Migrate Custom Fields

19

Basic ModePros:

Rename the field

Add datatype

Choose which fields to migrate

Cons:

One field at a time

One Extension group

20

Advanced ModePros:

Name the extension group

Rename the field

Add datatype

Cons:

One field at a time

21

Migrate Custom FieldsPros:

Simple, one step process

Cons:

No control over the process

All in one extension group

Cant rename any fields

Cant remove any fields

22

Choose a Hybrid Move the fields that you need to change (use Basic or

Advanced mode as needed)

Delete custom fields not needed

Migrate custom fields

23

How the Changes Affect Existing Functionality

Field Names

Search (1-1, not child)

List Students

Object Reports

Reporting Engine

ReportWorks

Quick Export, Export Using Template, and Date Export Manager

Quick Import, Import Using Template, and Date Import Manager

AutoComm/AutoSend

DDE/DDA

Backward compatibility is supported for the foreseeable future.

24

Key Points from Todays Class

Migrate core fields en masse

Migrate user custom fields using the methods that best fit your needs

Remember that once created, custom fields in database extensions cannot be deleted

25

Question and Answer

26

Copyright 2014 Pearson Education, Inc., or its affiliates. All rights reserved.

Dont Forget!!

Navigate to

http://powerschooluniversity.com

and tell us what you think!