topic Uncommit Master Schedule? in Community Forum

Uncommit Master Schedule?

millerc0524 — Fri, 07 Jul 2023 13:13:28 GMT

We just moved over to Powerschool from SIS. I am attempting to learn by doing and just committed my schedule after many loads. However, now I have found some other issues that I want to fix by moving around a few elective classes. In SIS we could unaccept the schedule and rebuild. Can I do this in powerschool? Like can I simply go into powerscheduler, make the class changes, do some loads and then recommit and override the existing schedule? Thanks in advance for your help.

Chris

Re: Uncommit Master Schedule?

ErinR — Fri, 07 Jul 2023 16:33:43 GMT

Hi Chris,

You can certainly do this if you'd like with PowerSchool. There isn't a way to unaccept the schedule, but you can certainly make changes and re-commit if you'd like. Part of the commit process deletes the old cc and section records and will replace them with the newer info from PowerScheduler.

We normally wait until just before we run year end in August to commit our school schedules, so typically don't have to re-commit. But during covid when schedules were changing drastically the first year back, we did it for some schools in the fall with no problem.

Re: Uncommit Master Schedule?

JoeD1 — Wed, 05 Jun 2024 19:56:14 GMT

I just wanted to share that we had our classes syncing with Clever and I was looking to prevent showing next year's info in clever for students. I was able to delete all the TermID=3400 or greater records from the CC table for the school I needed and when clever re-synced it removed the next year schedules for the students. Term 3400 is next year's term (we are in 23-24, wanting to delete 24-25 which is TERMID 3400). Hope this helps someone.

Re: Uncommit Master Schedule?

ErinR — Thu, 06 Jun 2024 14:01:15 GMT

We also use Clever for rostering to other products. In our case, we opted to modify the queries that Clever originally sent us (there was too much data that we were not going to use being requested). We have our sections query only pulling current year information so we avoid the problem that you've had. Just a second way to solve the problem.