In my Vendorization talk at the SyteLine User Network conference, I mentioned how simply poking around in SyteLine can sometimes cause unintended changes to Vendor objects. We discussed Vendorizing forms, but never really talked about global objects.

One of the things I have discovered recently is that sometimes during development, one could accidentally make a Site version of a global object without intending to. These global objects then sit as Site versions in the Forms Database, even though their contents are identical to the Vendor versions. (I find this tends to happen if you open up an object, like a Component Class, in the Winstudio editor, look at how it’s doing something, and then closing by clicking “OK” instead of “Cancel.”)

As I’ve mentioned before, every Site version is a liability. If you upgrade the Vendor version of the global object, and don’t FormSync it over, you will still be running the old version of this object.

So, what I have done is put together a little script that identifies non-Vendor objects in your forms database that are identical to the Vendor versions of those same objects. If you run it against your Forms database, any objects it returns should be safe to delete. (The code does not perform the delete, you’d have to do that in FormSync. Even still, I’d recommend checking them by using the “Compare” window in FormSync.)

Here’s the script, standard disclaimer: While this script is read-only, we are not responsible for any damage you do to your system with the results of this script. Take backups and work in a dev environment!