As discussed in 917, moving Users between Business Units can be difficult and, as Joel suggested in 935, a good option when setting up a new system is to add a child Business Unit from the outset and add all the Users there. In a recent implementation I did not do this (in my defence, […]
Say you move a user to a different business unit, but you forget that when you change a user’s business unit, it removes all of the user’s security roles. How do you find what role the user used to have? One answer is audit history. If auditing is enabled for user entity, you will see […]
Generally my policy is unless there is a REALLY good reason, all data in CRM should be shared. However, on rare occasion, there is a REALLY good reason. When you have one special group who want to hide their, say, Activities from everyone else, a well-placed Business Unit will do the job (either have one […]
In Tip 917 we talked about what happens if you have too many business units in Dynamics 365. But what about the opposite — can you have too few business units? If you are implementing Dynamics for a single group, it is common to only use the base business unit for all users. “We don’t […]
Someone recently asked me what I thought of someone adding 1,000 + business units to Dynamics 365. I told them it was a bad idea. Here’s why: Business units are like large granite rocks–they are designed to be permanent and infrequently moved. While users can be moved between business units, it is not a trivial […]
of the