Have you seen that message before on your Microsoft Dynamics CRM organisation?
You may have if you have tried to activate more than 10 business processes at the same time for the same entity.
This is a limitation by design which is well-known and described on the Microsoft technical documentation, have a look at the following article.
This limitation can be changed using the organisation property Organization.MaximumActiveBusinessProcessFlowsAllowedPerEntity. The easiest way to to change this attribute is using the following tool: Dynamics CRM Organization Settings Editor (OrgDBOrgSettings)
And now, you may be thinking: “why on earth would you do that??”
If your CRM deployment is heavily used, some core entities (e.g. Case, Opportunity) may be used intensively on different processes across an organisation.
Note: the current CRM version I’m using is: (184.108.40.2069) (DB 220.127.116.119)
Microsoft Dynamics CRM 2016 Update 1 brings Email Signatures as an out of the box functionality. They can be used on Users or Queues (based on Teams).
Create a new email and you will see a new icon on the email designer to insert signatures:
To create more signatures, go to Personal Settings or, as an admin, Administration => Templates section.
Administration => Templates:
Notice Email Signatures is a new entity and it is part of the security roles. So, for instance, if the Customer Service Team requires to use Email Signatures, they should have access to the Email Signature Entity. See below an example security role:
Note: My current on-line build version is : 18.104.22.1682 – DB 22.214.171.1249
You can find more information in the following Microsoft CRM article:
Probably many customers and partners have already asked you this question: where is our data? You can give them more details and a quick picture using the next Microsoft site:
You can already try the new Voice of the Customer (VoC) functionality in Dynamics CRM Online (only Online for now). Initially it was only available in US deployments (https://orgname.crm.dynamics.com) but this week has been released in EMEA datacenters as well (https://orgname.crm4.dynamics.com).
VoC allows you to design and publish surveys using Dynamics CRM. You can then share these surveys with your customers and gather their feedback efficiently within CRM.
The current CRM version I’m looking at is 126.96.36.199:
And the solution package is 8.1.344.1:
You can find more documentation in the next link:
We noticed incoming emails stopped getting in and we saw a 401 Authentication Error in the CRM Email Router server logs. Nothing has changed in the system account used for this Forwarded Mailbox and the password is still valid.
Deployment: CRM Online + CRM Email Router + Exchange Online
CRM Email Router Configuration: Forward mailbox is used for incoming emails.
After a few tests using the next utilities (very useful!):
We noticed that system account cannot access its own mailbox. Very weird, like if you don’t have access to your own home suddenly.
Finally, we just had to force an update on this system account to make it work again using the next PowerShell command:
set-msoluser -blockcredential $true -userprincipalname [userAccountName]
set-msoluser -blockcredential $false -userprincipalname [userAccountName]
It looks like the system account was desynchronised between our internal AD and Microsoft Online AD, causing this issue.
The xRMVirtual session on Tuesday September 1 had to be cancelled last minute because of technical and audio difficulties and we couldn’t share our experience on previous events such as Convergence, CRMUG and eXtreme CRM.
However, you can still find some of the tricks I was about to share in the next link How to get the most out of Convergence in Barcelona and you can find the deck here:
If you need to give the ability for a Dynamics CRM user to Import Data, you can just create a security role with access to the next entities:
- Data Import
- Data Map
- Import Source File
Note: I have notice you will need, at least, Delete right – user level on the Data Import entity (it doesn’t make sense if you just want to allow the import, but this is what I found; it could be a bug). Otherwise the IMPORT DATA button won’t appear. See the same in the next screenshot:
See below an screenshot with the configuration described above.
Have you seen the latest CRM Developer Center? It is a great place for developers getting started with Dynamics CRM. The search has been customised and improved to find content only related to CRM, see below an example.
Also there are many resources for those interested on Mobile development, have a look at Mobile SDK.
Notice how “entity” brings results only relevant about Dynamics CRM (e.g. rather than Entity Framework)
My Edge favourite feature so far is “Make a Web Note“. It allows you to write notes on the current page you are browsing, highlight things and add typed notes to describe steps.
I find this browser utility very useful for Dynamics CRM users who needs to share tricks or help other colleagues. See below an example.
A colleague doesn’t know how to find Leads, so we are going to get him an screenshot highlighting where to go within Dynamics CRM:
On the right top corner, select “Make a Web Note” icon:
A new noting bar will open with the utilities at the left corner. See how the Lead tile has been highlighted:
Then you can Share the same using different options, either taking an screenshot or sending it to other apps, like OneNote:
The new CRM SDK 2015 doesn’t give support yet for our known CRM Developer Toolkit, which has been part of the CRM SDK until CRM 2013. Basically, the CRM SDK 2015 assemblies have been compiled with .NET Framework 4.5.2, but CRM Developer Toolkit was compiled using NET Framework 4.5. See the next Microsoft article for more details.
For instance, let’s check the new assembly Microsoft.xrm.sdk.dll part of the CRM SDK 2015:
The good news are… we still can make compatible the Developer Toolkit with the latest CRM SDK 2015 editing the .NET Framework in the corresponding projects of our Visual Studio solution. Let’s say we have the next CRM solution:
For plugins and workflows, we should update the references to the new assemblies and also the .NET Framework in the project properties:
After updating those references, we could still find the following error:
“The type or namespace name ‘Xrm’ does not exist in the namespace ‘Microsoft’ (are you missing an assembly reference?)”
This error is indicating you haven’t got installed the expected .NET Framework 4.5.2. Do right click on the same project and select Properties to check the version actually used:
If you are only getting old versions of the Target Framework, select “Install other frameworks…” that will take you to the next site:
There you must download .NET Framework 4.5.2 Developer Pack.
After it has been installed, you get a new option in that previous list:
Finally, we need to do something similar with the CRM Package Project. But in this case, we will have to edit the project file and update the entry “TargetFrameworkVersion” to “4.5.2”. Start unloading the project:
Update the mentioned entry “TargetFrameworkVersion“:
Finally, reload the project again and everything should work now!
About this last part, I would like to say thanks to my CRM MVP colleague Scott Durow (@), who helped me to find that entry.
If you don’t update the package project, it may still compiled, but the actual deployment will fail and you should see the next warning in the Visual Studio output:
warning MSB3274: The primary reference “[Your Assembly Name].dll” could not be resolved because it was built against the “.NETFramework,Version=v4.5.2” framework. This is a higher version than the currently targeted framework “.NETFramework,Version=v4.5”
warning MSB3275: The primary reference “[Your Assembly Name].dll” could not be resolved because it has an indirect dependency on the assembly “Microsoft.Xrm.Sdk, Version=188.8.131.52, Culture=neutral, PublicKeyToken=31bf3856ad364e35” which was built against the “.NETFramework,Version=v4.5.2” framework. This is a higher version than the currently targeted framework “.NETFramework,Version=v4.5”