Sie sind auf Seite 1von 27

Custom Field Migration

Trainer Name Trainer/Consultant

PowerSchool University

2014

Custom Field Migration Trainer Name Trainer/Consultant PowerSchool University 2014

Agenda

• Custom Fields – A Little History

• Legacy Custom Field Data Migration

• Migrating User Custom Fields

• Changes After Migration

2

– A Little History • Legacy Custom Field Data Migration • Migrating User Custom Fields •

Custom Fields - A Little History

Legacy Custom Fields

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

4

In addition, legacy custom fields had other issues: • Datatypes not defined • One-to-many records not

Database Extensions – Benefits

• 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

5

Allows direct access to tables and fields from SQL • Improves performance • Includes enhanced customization

Legacy Custom Field Data Migration

Types of Legacy Custom Fields

7

Types of Legacy Custom Fields 7

Migration Process – State Reporting

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

8

Migration Process – State Reporting State and Province migrations will be on state- and province- specific

Migration Process – Activities

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

9

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

Migration Process – PowerSchool Core

• 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

10

Compliance Fields • One time, irreversible process • Migration Report and Get Data are critical to

Migration Process – User-Created Fields

• 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

11

can be moved manually when new fields are created • There is also a process to

PowerSchool Core Custom Field Data Migration

Select the Custom Field set, run the Migration Report, and get the data (if needed)PowerSchool Core Custom Field Data Migration Back up your data and migrate the custom fields Review

Back up your data and migrate the custom fieldsset, run the Migration Report, and get the data (if needed) Review the Migration Summary Look

Review the Migration SummaryReport, and get the data (if needed) Back up your data and migrate the custom fields

Look at the Migration HistoryReport, and get the data (if needed) Back up your data and migrate the custom fields

12

(if needed) Back up your data and migrate the custom fields Review the Migration Summary Look
Select the custom field set, run the Migration Report, and get the data (if needed).
Select the custom field set, run the Migration Report, and get the data (if needed).
Select the custom field set, run the Migration Report, and get the data (if needed).
Select the custom field set, run the Migration Report, and get the data (if needed).

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

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

13

Select the custom field set, run the Migration Report, and get the data (if needed). 13
Back up your data and migrate custom fields. 14
Back up your data and migrate custom fields. 14
Back up your data and migrate custom fields. 14
Back up your data and migrate custom fields. 14

Back up your data and migrate custom fields.

Back up your data and migrate custom fields. 14

14

Back up your data and migrate custom fields. 14
Review the Migration Summary. 15
Review the Migration Summary. 15
Review the Migration Summary. 15
Review the Migration Summary. 15

Review the Migration Summary.

Review the Migration Summary. 15

15

Review the Migration Summary. 15
Look at the Migration History. 16
Look at the Migration History. 16
Look at the Migration History. 16
Look at the Migration History. 16

Look at the Migration History.

Look at the Migration History. 16

16

Look at the Migration History. 16

Now It’s Your Turn

Complete Demonstration activity 1:

Migration of PowerSchool Core Fields Process

User Custom Fields Migration

Three options

• One field at a time: Basic Mode

• One field at a time: Advanced Mode

• All fields at once: Migrate Custom Fields

19

One field at a time: Basic Mode • One field at a time: Advanced Mode •

Basic Mode

Pros:

• Rename the field

• Add datatype

• Choose which fields to migrate

Cons:

• One field at a time

• One Extension group

20

the field • Add datatype • Choose which fields to migrate Cons: • One field at

Advanced Mode

Pros:

• Name the extension group

• Rename the field

• Add datatype

Cons:

• One field at a time

21

Advanced Mode Pros: • Name the extension group • Rename the field • Add datatype Cons:

Migrate Custom Fields

Pros:

• Simple, one step process

Cons:

• No control over the process

• All in one extension group

• Can’t rename any fields

• Can’t remove any fields

22

No control over the process • All in one extension group • Can’t rename any fields

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

you need to change (use Basic or Advanced mode as needed) • Delete custom fields not

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

• AutoComm/AutoSend • DDE/DDA • Backward compatibility is supported for the foreseeable future. 24

Key Points from Today’s 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

methods that best fit your needs • Remember that once created, custom fields in database extensions

Question and Answer

26

Question and Answer 26

Don’t Forget!!

Navigate to http://powerschooluniversity.com and tell us what you think!

and tell us what you think! Copyright © 2014 Pearson Education, Inc., or its

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

and tell us what you think! Copyright © 2014 Pearson Education, Inc., or its affiliates. All