Tuesday, September 25, 2018

How to change the root Business unit name in Dynamics 365

This is old trick, but still valid even in the latest version of Dynamics 365.
By default, your root business unit name is the same as the CRM instance name.

If you want to change it, you can go to the Security Settings > Business unit.

Select the root Business unit, open it. You will see that the Parent business unit is mandatory and you are not able to save your changes.

You need to go to the Customization > Business units > Fields and change the parentbusinessunitid to Optional.

Then publish the customizations and go to edit the root business unit.

You will be able to change the name of the root business unit and save it.

Stay tuned for the next tip!


Friday, September 21, 2018

Calculated/Rollup field formula modification button missing

Recently we faced an issue where we were not able to modify the formulas for Calculated and Rollup fields.

When we opened the form where you customize the field, there was no edit button and the field was marked as „Simple“ even though is was rollup or calculated.

It turned out, that there was a bug in the script which is managing the form. It never displayed the button. The error was in Czech version of the Dynamics CRM. In English it was working fine, so we have developer a „workaround“ for this situation.

As you may know, Dynamics CRM has abase language which is selected when you Create new instance. This language is then used in the UI of the customizations. You cannot do customizations in any other language by default.

If you need to open the customization area in other language than is your base language, you can do this:

1.       Enable the language which you need

2.       Switch to the base language

3.       Go to Customization

4.       Open the Solution which you need to customize

5.       Switch the language to the one which you want to use

6.       Return to the opened customization window, once you move to another part of the customization, it will get the language you just have switched to.

You will have to repeat the procedure every time you close the customization windows.

Please note, that this also might be unsupported. I’m not sure.

Enjoy your day with CRM!

Update: The issue with missing button has been resolved in version 1710 (

Thursday, September 20, 2018

Unified interface significantly improved

Microsoft is preparing new major release of Microsoft Dynamic 365 (CRM).
Majority of user should start using the new modern client aka Unified interface, so Microsoft needs to close the gaps between the old UI and new UI.
If you have been missing the Advanced find and Merge feature in the new UI, you don't have to be worried anymore.
In the latest version, these features are included in the new Unified Interface.
They have the same design as the old UI, but they work OK in standard browsers.
From my point of view, it is a step forward. I'm looking forward to optimization of these features to make them work in all clients (mobile, tablets etc.)

Have a good day

There is a new Admin interface for Microsoft Dynamics (CRM) Customer engagement

The biggest change is that the instances are no longer instances, but they are call Environments.

Also, Microsoft has pull out many instance settings into the new Admin center. Admins can now access many setting like data auditing, business configuration, languages, currencies etc. from the admin center.

However, most of them are just link into the Dynamics CRM for now. We will see how it will be improved in future.

I have noticed, that the audit setting has new option – Audit read access, that is very awaited feature.  I turned it on in our environment, but it does not work yet.
How about you? Is this working for you?

The documentation is very limited about this:
So for now, if you need to audit the read access in Dynamics 365, you need to rely on some addon or use the Office 365 audit features, which also supports read access in Dynamics 365.

At the moment, the new admin center does not support coping, reseting and creating new instances (sorry, Environment 😊), backup management, application management and so on, so it is really a preview.
Have a great CRM day!

Wednesday, September 19, 2018

Dynamics Troubleshooting – canmodifymobileclientvisibility

Dynamics Troubleshooting – canmodifymobileclientvisibility

Recently, I have been deploying some solution from one environment to another in Dynamics 365 online.
It failed soon after the start with this error:

The evaluation of the current component(name=Entity, id=59c9b48d-5578-41f2-9ca2-689e1dac0905) in the current operation (Update) failed during managed property evaluation of condition: The evaluation of the current component(name=Entity, id=59c9b48d-5578-41f2-9ca2-689e1dac0905) in the current operation (Update) failed during managed property evaluation of condition: Managed Property Name: canmodifymobileclientvisibility; Component Name: Entity; Attribute Name: canmodifymobileclientvisibility;

Doing some investigation, I did not find anything in the discussions, so I decided to share my observation with you.
In the meantime, I also created a case with Microsoft Support, so when this will be resolved, I will update this article as well.

The import failed when trying to import the campaign entity first. When removed, it failed with campaign activity, so the problem seems to be connected to the Marketing module of D365.

Going into the customizations I found the following.

Source environment Campaign entity mobile setting looks like this:

Target environment is looking like this:

The source version: Version 1710 ( online

The target version: Verze 1710 ( online

It is obvious that Microsoft is doing some changes in the core application which may break your customizations.

At the moment we are stuck in the situation that we cannot move solution from CRM to another, because they are not compatible.

We cannot update the older CRM to a newer one, because it is online version and we have to wait for Microsoft to update. I’m afraid it would not help, I have created a blank CRM instance with version and it looks the same as our source environment, so maybe only the current target instance is somehow broken. We will see what the support will do. We are not able to modify the properties which are causing the error.


We have come up with a workaround for this situation:

1.       Export the solution

2.       Open the customization xml

3.       Edit it – replace <IsVisibleInMobileClient>0</IsVisibleInMobileClient> with <IsVisibleInMobileClient>1</IsVisibleInMobileClient> for the entities which are causing errors.
You can also use <!-- to comment out the problematic section.

4.       Import into target environment

However, at the moment you would be forced to do it before every import.
Stay tuned for the result of MS Support

Update: Microsoft is aware of this bug and they have prepared solution for it. It will be deployed soon!