In this blog, we share a lesson learned when using a Dynamics 365 Customer Engagement online data source connector, called Instance Web API, for Power BI reports.
The Microsoft Dynamics CRM 2013 release is a few short months away, and it will come with some great new features. In this blog we'll discuss one of these new features—portable business logic. Then we'll show how you can use it to create rules that hide and show fields on a form.
Portable business logic allows you to define business rules for each record type. You can use it to do any of the following:
You can set all of these actions to occur based on conditions you set in the business rule. Conditions can be based on one of the following:
Let's take a look at an example of how this works. In this scenario, we want two custom fields—Role with Vendor and Priority—to show if a Contact is of Relationship Type Vendor.
We already have the two custom fields added to the form with their visibility disabled. Now we just need to setup the new Business Rule. Use the following steps create a new Business Rule for the Contact:
NOTE: Keep in mind you may need to create inverse Business Rules to hide the fields if a different value is selected. In this case, you may want to make sure the 'Role with Vendor' and 'Priority' fields stay hidden if a different 'Relationship Type' is selected. Here would be the appropriate business rule:
There you go! Showing and hiding fields is now much simpler to implement using the new business rules.
If this was helpful, you can also check out our other blogs and resources for Microsoft Dynamics CRM 2013.