Realy nice idea, but does this still work? I tried it in our enviroment (PU32) and it seems that the code won't be executed?

Hi Ronald. I tested on 10.0.11 and it looks good. Can you try to debug it and provide more info please. The breakpoint to hit SysTableBrowserDEV_Extension - run(). Also note - that your user should be in DEVSysTableBrowserExt user role in order to enable editing

I am member of the role, I renamed it according our Naming Guide Lines, but this shouldn't be a issue. I am able to see the Buttons, but they are not enabled.

I also tried to create a new object with the same result.

The breakpoint will be hit, but on the DEV enviorment allowedit is always true, or not?

You need to debug like this(Debug a copy of the production database)
https://docs.microsoft.com/... .
It will be interesting to find a reason, but I don't have now access to any SAT env now. You can also try to duplicate SysTableBrowser class to check

I am sorry, but debugging a UAT Enviorment won't work, because the line " isSystemAdministrator() && isDeveloper();" is true.

Any suggestions how to resolve? I suggest to duplicate the standard
SysTableBrowser class and form and check what it will be(if you have time for this)

at the moment I have no idea, I created a extension for "isDeveloper" to simulate a UAT, but this works (in an DEV), but I have no Idea what else I can try for an UAT, i already created a copy of SysTableBrowser which extends the base, I will try it with a complete new object.

Just let you know - I updated the model(by duplicating standard objects). It should work now. https://github.com/TrudAX/X...

Nice post! Already forwarded to our tech group. Will this violate any kind of policies ?

Probably some customers had problems related to table browser usage by users, that is why MS decided to disable it. Just keep this in mind