The behavior can be different, based on inconsistencies in each end user’s environment (which are difficult to regulate!). This can be true even if the app provider says it’s compatible. While solution providers try their best to make everything compatible in most common environments, there are sometimes noticeable differences in behavior. Even worse, it may not be compatible at all in one users’ environment and therefore not execute.
It requires a developer to code and maintain as your business logic changes.
If a Business Rule references a field that has been removed from the form, the rule will not run and an error will not appear. This could also be seen as beneficial, depending on your situation.
Business Rules are cached on Dynamics 365 for tablets. If your System Administrator/Customizer changes the logic, this will not be committed to tablet users until they close and re-open it. Most of the time, this should not be an issue unless you have users who work 24/7!
New features of Business Rules
Two that I think are worth highlighting include:
Create a snapshot of an entire Rule. You can use this to share with your team members for input before it is committed to the system.
Create business recommendations based on business intelligence. This adds helpful tips next to fields to guide users on filling out forms based on previous data filled in. A great example provided in Microsoft’s blog is the use of these for product recommendations. For an example, an end user may be filling in a new Opportunity for a prospect. Based on previously identified information such as their age and insurance type, a recommendation can be made for products that other prospects within their group typically purchase.
Beringer Technology Group, a leading Microsoft Gold Certified Partner specializing in Microsoft Dynamics CRM and CRM for Distribution. We also provide expert Managed IT Services, Backup and Disaster Recovery, Cloud Based Computing and Unified Communication Systems.