Moving previous year data on Powerscheduler

[ashleymb12]

Hi all!

Last year was the first year that we completed a build on Powerscheduler for my high school. It was great! However, we are trying to copy over the previous years constraints and teacher assignments. When I go to functions then select move previous year data and select submit it nothing is transferring over. I have checked the years and terms to be sure there are the same. Has this every happened to anyone else? Does anybody have any suggestions?

Thanks in advance!

[jlehman]

Hi Ashley - I've had this issue and I've remedied it in a few ways. I believe the issue comes up when certain seemingly unrelated things are not all lockstep. For instance, if you copy the constraints after you assign a new catalog to the scenario, they won't appear since those constraints are associated with the prior (year) course catalog and your active scenario has a different course catalog. 

An absolutely sure-fire way to fix this (and learn more about the guts) is to download the constraints from last year to a csv. The table is ScheduleConstraints. Download all of the columns and all of the constraints. You'll see BuildID, CatalogID, TermID and YearID which are keys of sorts to all of the details of each row of constraints. ConstraintType defines the type of constraint you are looking at. 

If you modify BuildID, CatalogID, TermID and YearID to be your new scenario values (as seen on your landing page for PowerScheduler - mine is currently Build: 2025 - 2026 (1602)    Catalog: 2025-2026 (551)), you can save that and upload it back to that same table, and boom!, you're in business. 

Alternatively, you can mess with creating a new scenario from copying last year's and just make sure you start with everything being the same - especially the course catalog. Look at the ScheduleConstraints table in DDE and see if you can find what is a mismatch. It's usually the course catalogID in my experience. Let me know how you do, or if you need more info.

[ItsOnlyDoug]

I copy over previous year data every year. 

Have you double checked you have the correct scheduling year selected?

Also, double check to make sure you have the correct Build Scenario active.

[ashleymb12]

Hi, 

Yes, I have double checked both of those things and the build from last year is selected to copy over and our current build 2025-2026 is checked as active. 

[ashleymb12]

Hi, 

We used the same course catalog from the previous year. I have also checked the build to make sure the current build active. I will try downloading the constraints to a csv. Thank you for that information! 

All of this was very helpful and will hopefully fix the problem!