The Secret PowerSchool Technical Manual: Unintended Consequences of Plugins

PowerSchool LogoOne of the reasons our school chose to go with PowerSchool, is that it has a higher degree of customization than many other SIS products.  And when we first started with PowerSchool, we had a great consultant come out and help train our techs on how do much of this customization, and at the same time, he helped us do some of the initial customizations we needed.  And in the end, to help us implement these customizations, he wrapped them up in to a plugin, and we were able to easily install them.  And we thought that it would be easy for us to continue to customize things….

But, it turns out that if a plugin adds an extended table (database extension), then you cannot add more fields to that extended table later, without doing it through updating the plugin (at least in the current version).   Right now, we are trying to figure out how to best solve this problem.  I’m hoping we can just find a way of removing the plugin without removing our data (or have PowerSchool do this)…  But for others who are tempted to make a plugin to “easily” add some customizations, be aware that it might have unintended consequences.

Leave a Comment

Your email address will not be published. Required fields are marked *