While connecting to Dynamics 365 – Version 9.0.0.0 online through a console application using Visual Studio 2015
we were getting the below error
The fix was to specify the security protocol to be Tls12 for the connection for VS 2015 and for VS 2017 make sure the framework version is 4.6 or above.
More Details – https://support.microsoft.com/en-nz/help/4051700
Hope it helps..
As part of Spring 2018 update, Microsoft recently introduced a modern style of app building – Model Driven Apps. Model-driven app design doesn’t require code and the apps you make can be simple or very complex. Unlike canvas app development where the designer has complete control over app layout, with model-driven apps you will have pre-built design template which is customizable based on components you add to your app.
Let’s take a closure look how Model Driven Apps differ from Canvas Apps
| Canvas App | Model Driven App |
| Complete control over app layout. You can create app from scratch with no coding | Model-driven apps automatically generate great UI that is responsive across devices |
| Available with all versions of Common data service | Model-driven Apps are available only with the new Spring version of Common Data Service |
| You can connect to Dynamics 365 and browse, add, delete, update data in Dynamics 365… |
View original post 154 more words
Recently I was conducting a training in Dynamics 365 where I got the same question. Just a quick thought and the answer that comes to mind is “Yes”. After all,
a user’s security role is the sum of the security roles directly assigned to the user + sum of the roles the user derives through it’s association with the Teams (provided teams are given security role)
And here I was, where a user is belonging to a team and the team has a security with all the right privileges assigned to make the user work in Dynamics.
When I assigned the role directly to the user and the user is not part of the team, it just worked fine. Now comes the other way round. I remove the user’s security role, assign the same security role to a team and add the user to the team.
As you can see…
View original post 250 more words
Recently one of our users reported the below while trying to bulk update the records using Excel Online feature.
The user had the Update rights for those records.
Basically, the Excel Online update features creates a data import job in the background.
https://debajmecrm.com/2015/11/14/dynamics-crm-excel-online-field-changes-save/
So the user had to be given the import data rights.
We resolved the issue by giving the following rights to the user at organization level.
https://community.dynamics.com/crm/b/crmpowerobjects/archive/2015/08/18/data-import-privileges
Hope it helps..
Recently while trying import products from our Dev to Test environment using the Configuration Migration tool we got the below error
The reason being we were using default unit as a unit group in out DEV and the same wasn’t there in the TEST environment. Interestingly if we set the correct GUID in the data.xml generated by Configuration Migration tool and try importing, still the products do not get imported.
So basically, if we try importing the products entity alone we might run into issues. To migrate it properly we need to add the related entities along with it as mentioned in the Microsoft documentation.
We created a new schema file with Product and its related entities, and this time migration worked properly.
Hope this helps.
Recently we wanted to hide OOB reports for our users.
One way of doing it is either change those report from Organization owned to personal
or change the Display in Area for those reports (this will hide those reports from all other views except the “All Reports, Including Sub Reports” view), as all other OOB Views for the reports uses the Reports Area filter. Another option of course is to update the filter criteria for those views or deactivate those views.
In our case, we simply updated the Display In property for all the OOB reports. Below is the sample code that we used. Basically, every report can have 0 or more (max 3) related Report Visibility records associated to it. (i.e. for forms, lists or reports area). In the below code we have looped through all the OOB reports and deleted all the associated ReportVisibility records for that report.
Hope it helps..
