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: (8.1.0.369) (DB 8.1.0.369)
Software Engineer specialised on Microsoft Technologies with experience in large projects for different industrial sectors as developer, consultant and architect.
I enjoy designing and developing software applications, it is my job and one of my hobbies. I’m interested in design patterns, new technologies and best practices. Making those part of the ALM process is a great challenge.
Since 2008, I have been working with Microsoft Dynamics 365 (CRM back then), the Power Platform and Azure. I customise and extend the platform to provide tailored solutions and integrations based on service-oriented architectures and messages queuing.
Motivated by community events and contributor in blogs, technical books, open source projects and forums, I was awarded Microsoft Business Applications Most Valuable Professional (MVP) for 7 years.
View all posts by Ramon Tebar
@ramontebar 👨💻 