I encountered an issue this week when I was upgrading our extension for our onpremise customers.

The upgrade involved breaking schema changes (moving fields from one extension to another) that required the old extension to be unpublished first.

For one customer, I couldn't accomplish this because the tenant had almost 20 designer extensions installed. Several of those designer extensions forced a dependency on the extension I was trying to upgrade, this prevented me from unpublishing my old extension first.

I had to hunt down and uninstall+unpublish every designer extension.

It's my belief that the onpremise in-client designer should be HIDDEN by default.

In BC SaaS, designer extensions are not allowed for production instances so I'm puzzled as to why onpremise shows the designer button by default.

I'm not a fan of designer extensions at all. There is zero accountability with them (there's no way to easily ascertain who/when/why the designer extensions were created and it creates a mess of extensions with poorly named extensions and publishers).

The end-users just don't understand the purpose and implications of customization vs designer.

Please consider turning off the in-client designer by default for onpremise. They're very hostile to our tenant administration duties.