I am a Microsoft Dynamics 365 & Power Platform aspects engineer Rayong, Microsoft Most Valuable Professional is the July 2015 to June 2018 for three consecutive years Dynamics CRM / Business Solutions aspects (Microsoft MVP), I welcome the attention of the public micro-channel number MSFTDynamics365erLuoYong, reply or 20,191,025 372 may facilitate access to this article, but you can get the latest information I Bowen issued in the first room, follow me!
Dynamics 365 has a dispatch (assign) authority, it and share (Share) is not the same, after the dispatching, head of records (owerid) changes, and record the current operator may have no reading of the record is changed after the person in charge authority, and this will lead to error pages, without permission error. Of course, system settings there is an option whether to share [reassign records from the original person in charge] can help you, but the default value is, of course, is not encouraged to open up.
Assign permissions is also divided into no personal level, the business level, business unit on the lower level, organizational level, and this level makes no difference read permissions, assign individual level can only assign person responsible for recording the current user, or share the assignment of rights the current record to the user, or the person responsible for recording the user's current team record.
Assignment and write permissions it matter? Basically it does not matter, so sometimes you have to explain that the people on this record is not writable, but assign permissions, in fact, be changed after the recording was assigned head of the field. You do not have write permissions (including the entity does not have write permission, or some entity recorded no write permission), but as long as you have assigned rights to the record, or can be assigned to the record. Which records you can still see you perform assigned assign permissions to the entity, the entity if all records globally, is that you can see can be assigned, if the business unit level assignment, you can assign you or the person responsible for the record you with a business user's records, of course, including the assignment of rights to share your records, headed by team record in your area. Although there are separate, but shared with other users assign permissions when sharing will also write permissions.
There is also a dispatch function, assuming that the user A change from B to C business business, if you do not deal with, he would take away the record, and in some scenes is not allowed to take away, I call this scene a man walk on the cold tea. For example, when an agent in charge of case A country can be seen in case they own, these cases are in country A, after changing the business sector, it required him not to see the case in country A, even before these cases he handled. This time may be A user's records are assigned to another user to accept his work, so it will not take away. Can use the following functions, find the user, click on the command bar [REASSIGN RECORDS] you can assign a lot of records.
When the user to replace the business sector, if the user has to change the record more, then, sometimes there will be SQL execution timeout error, my understanding is that the value of the hidden field will owningbusinessunit users all have a record of changes, the appearance to, or whether the user records, but the value of these fields owningbusinessunit record has changed. If the timeout can refer to my article Dynamics 365 to perform operations reported SQL Server has timed out, change the timeout setting of this method to extend SQL timeout period, and the implementation of changes to the user's business system is not busy at the time.
Click the button assignment out of the selected user or group can not do custom interface customization (at least I do not know). Sometimes there is a demand, such as A user can only be assigned to users will be recorded the same business unit, how to do? If you can accept it, adjust the user to read the [System] user permissions entity, you can set the read for the business sector level, the default user is reading [System] user permissions are global entities read. Of course, you can also terminate and prompts the user assigned to the wrong users to plug / real-time work, but the user experience could be worse.