You’re offline. This is a read only version of the page.
We implemented Dynamics 365 af few years back. A principle of ours is, that we want to share everything across the organization, so all users have global read access to most tables/entities.
However, one thing we want to restrict access to, is the sales price of an opportunity. We want all users to be able have read access to all opportunities, but we only want them to be able to see the sales price of the opportunities they own - or that users under them in the manager hierarchy owns.
To achieve this, we ended up creating a separate entity/table to store the sales price which is related to the opportunity. Then we can control the access to this entity using hierarchy security. This works fine - especially with new features like the form component, which allows the user to edit the sales price directly from the opportunity form without knowing, that the field/column is actually in another table/entity.
However, not using the out-of-the-box fields/columns makes it harder to get value from new features. Often, we must find workarounds as, as the sales price is not on the opportunity entity/table.
Since some time has passes since we implemented D365, I was wondering if any changes have been made to the security model, that could make this scenario possible today.
Is it possible to achieve this, without having to separate the data in two different tables/entities?
Share
Report
All responses (
Answers (
83
