Dynamics F/SCM Customer Experience (CRM) Dynamics GP Dynamics Business Central (NAV) Dynamics SL Power Platform Fabric Copilot

[Kerstin Newman]

We’re trying to grant access to some of our warehouse users to see tables rather than having to find issues through the UI browsing. Even though I have assigned the specific privilege for using the table browser and the specific tables they should have access to, they are getting an error and can’t access ANY tables, custom or OOB.
Any ideas from anyone on what I am missing? We’re on 10.0.5 (PU29) but are upgrading to 10.0.8 (PU32) in the next few weeks.

——————————
Kerstin Newman
Business Analyst
StarTech.com
London ON
——————————

[Alex Meyer]

Kerstin,

Can you verify what error you are seeing when the users try to access the table browser?

I have verified that the table browser feature itself still works in a PU24, PU31, and PU33 environments (just happened to have those versions).

——————————
Alex Meyer
Director of Dynamics AX/365 for Finance & Operations Development
Fastpath
Des Moines, IA
——————————
——————————————-

[Kerstin Newman]

Hi Alex,
Thanks for your response!

It does work for anyone with sys admin privileges just fine, but anyone else is getting the below error, even for OOB tables:

The users are getting the error even though they have the “Open table browser” privilege assigned to their role.. Any ideas as to how I can solve this?

Thank you!

——————————
Kerstin Newman
Business Analyst
StarTech.com
London ON
——————————
——————————————-

[Alex Meyer]

Kerstin,

It appears that the Allow Root Navigation option on the sysTableBrowser menu item display is set to No. This means that non-SysAdmins cannot directly navigate to this menu item without a context.

I’m not sure what the best option going forward would be to a non-SysAdmin user, maybe creating a ‘dummy’ local extension so you can change this property?

——————————
Alex Meyer
Director of Dynamics AX/365 for Finance & Operations Development
Fastpath
Des Moines, IA
——————————
——————————————-

[Alex Meyer]

Kerstin,

So I was able to get this to work by doing the following:

1) Creating a copy of the sysTableBrowser menu item display into a project
2) Changing the Allow Root Navigation parameter from No -> Yes

3) Create/assign this copied menu item to a privilege/role (here is an example)

4) When this is assigned to a user and they navigate to <RootD365FOEnv>/?mi=SysTableBrowserCopy&tableName=<tableName>&cmp=<companyId> they should see the table browser
(for example to see the UserInfo table: /?mi=SysTableBrowserCopy&tableName=UserInfo&cmp=DAT)

Feel free to reach out with any questions.

——————————
Alex Meyer
Director of Dynamics AX/365 for Finance & Operations Development
Fastpath
Des Moines, IA
——————————
——————————————-

[Polo Garcia]

Hi, Alex,

I am interested in doing this as well. Can you please tell me where that sysTableBrowser menu is? 

Thank you,
Polo

——————————
Polo Garcia
Maple Leaf Farms, Inc.
——————————
——————————————-

[Alex Meyer]

Polo,

I’m not sure if you want to try and access it through the user interface or through the AOT so I listed both options.

The SysTableBrowser is not accesible through a path in the UI you can only get it to their manual URL manipulation using the syntax I listed in my previous post.

In the AOT, you can find it by searching to sysTableBrowser and selecting the menu item to duplicate.

——————————
Alex Meyer
Director of Microsoft Software Development
Fastpath
Des Moines, IA
——————————
——————————————-

[Polo Garcia]

Wonderful! Thank you, Alex!

Polo

——————————
Polo Garcia
Maple Leaf Farms, Inc.
Leesburg
——————————
——————————————-

[Kerstin Newman]

Thanks so much, Alex! We’ll see if we can get our developers to build an extension to the table to enable access for non-sys admins. Thanks again for the responses and suggestion, much appreciated!

——————————
Kerstin Newman
Business Analyst
StarTech.com
London ON
——————————
——————————————-

[André Arnaud de Calavon]

Hi Kerstin,

However the method provided by Alex is working, wouldn’t it be better to provide a specific form to view the errors more easy? Microsoft might in future decide to remove from or further limit the table browser on the production environment. In that case, I would rather not depend on this form but provide the users a specific form where they can do their specific troubleshooting.

——————————
kind regards,

André Arnaud de Calavon
Product manager, Microsoft MVP – Microsoft Dynamics Business Solutions
——————————
——————————————-

[Kerstin Newman]

Hi André,
Thanks for the suggestion, I totally agree. We thought the table browser would be easy (because only sys admins tested it before) and a quicker solution for the time-being than building a report or screen for them with the required information. Long-term, that’s definitely our goal, we just thought the table browser could provide them with the information in the short-term.
Thanks again!

——————————
Kerstin Newman
Business Analyst
StarTech.com
London ON
——————————
——————————————-

[Katja Schebler]

We had similar discussions for D365. We did not provide the table browser, because the table browser might allow access to all tables. And we do not want that all users can read all finance data, all prices, all HR data in D365, etc. 

——————————
Katja Schebler
NORMA GROUP Holding GmbH
Maintal
——————————
——————————————-