Finance | Project Operations, Human Resources, ...

Removing users from DAT demo company

(0) Share

Report

Posted on by Ian Waring

436

we have only one company in our D365FO 10.0.20 cloud platform. We want to prevent users from accessing the demo company and indeed stop having our Fastpath setup doubling up the user conflict counts on the dashboards that all our senior management look at.

it looks as though if you have two or more companies, you can set the org hierarchy up so users can be pointed at one instance - at which point you can deselect DAT from being accessible to named users.

is there a way of disabling user access to the DAT company with only one other company in our setup?

I have the same question (0)

All responses (7)

Answers (0)

Elsa Guo on at

Like (0)

Report

Hi lan,

The similar issue for your reference. https://community.dynamics.com/ax/f/microsoft-dynamics-ax-forum/261892/delete-legal-entity-in-d365-ax7/737040#737040

https://community.dynamics.com/365/f/dynamics-365-general-forum/223348/delete-demo-instance-and-create-a-new-clean-instance/753578

thank you.

Was this reply helpful? Yes No
Ramit Paul 22,797 Most Valuable Professional on at

Like (0)

Report

Hi Ian,

Did you check the setup in user form? there you restrict access for users to access other LE.

Was this reply helpful? Yes No
Prem Kumar Bachu 3,418 on at

Like (0)

Report

Hi Ian,

We can grant access to specific legal entities to users by using "Assign organisations" in the user form. Select a company you want give access and grant access.

Regards,

Prem

Was this reply helpful? Yes No
André Arnaud de Cal... 300,911 Super User 2025 Season 2 on at

Like (0)

Report

Hi Ian,

The DAT company is not a demo company. It contains global data. Even with one LE, you can assign organizations. That can be done without setting up a full organization hierarchy.

Was this reply helpful? Yes No
Ian Waring 436 on at

Like (0)

Report

Nope. That doesn't work if you have only one company - that option is greyed out:

Was this reply helpful? Yes No
Suggested answer

Prem Kumar Bachu 3,418 on at

Like (0)

Report

Try with user role other than system administrator and keep the cursor on that role. Then this button should be enabled.

Was this reply helpful? Yes No
Suggested answer

André Arnaud de Cal... 300,911 Super User 2025 Season 2 on at

Like (0)

Report

Hi Ian,

The default validation to have the button enabled is not looking at the number of legal entities. It taking the next validations in consideration:

- A role has been selected and not the main 'Roles' node.

- The selected role is not System administrator

- The user is not a service account

- The level of the role is the first level. Sub roles should follow the assignment of the parent role.

If the behavior in your environment is different compared to the described logic, probably your add-on might have additional validations. You can check it with Fastpath.

Was this reply helpful? Yes No