Dynamics 365 Customization Insight: Navigating Business Rule Activation Errors

In the world of Dynamics 365, customizing business processes to fit specific requirements is a common task. However, this customization journey isn't without its hurdles. A particularly perplexing issue can arise when activating Business Rules, especially those involving lookup fields. This article delves into a specific error encountered during Business Rule activation and offers a JavaScript workaround for situations where traditional Business Rules fall short.

The Encounter with Error

While attempting to activate a Business Rule in Dynamics 365, you might be greeted with a daunting error message:

System.ServiceModel.FaultException`1[Microsoft.Xrm.Sdk.OrganizationServiceFault]: System.Web.HttpUnhandledException: Exception of type 'System.Web.HttpUnhandledException' was thrown. ---> Microsoft.Crm.CrmException: The selected workflow has errors and cannot be published. Please open the workflow, remove the errors and try again. at Microsoft.Crm.Dialogs.ActivateDialogPage.ConfigureForm() +0x573 at Microsoft.Crm.Application.Controls.AppUIPage.OnPreRender(EventArgs e) +0xa4 at Microsoft.Crm.Application.Controls.AppPage.OnPreRender(EventArgs e) +0x7 at System.Web.UI.Control.PreRenderRecursiveInternal() +0x54 at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +0x6d3 --- End of inner exception stack trace ---

This error message indicates a failure in the activation process, often leaving the administrator or developer puzzled about the next steps.

Root of the Issue

Upon closer examination, the issue was traced back to a Business Rule designed to control the visibility of certain fields based on the value of a lookup field. The crux of the problem lied in the mismatch of the GUID (Globally Unique Identifier) of an involved lookup field value after the Business Rule has been published from one environment to another environment (the two environment have different GUID for same record), rendering the Business Rule ineffective.

The Shift to JavaScript

The solution was to deprecate the problematic Business Rule and pivot to a JavaScript-based approach to manage the field visibility. This strategic shift was due to the inherent limitations of Business Rules when dealing with dynamic GUID values associated with lookup fields.

JavaScript Implementation Insight

The JavaScript solution involves capturing the context of the form and the target lookup field. Based on the value (in this case, the GUID) of the lookup field, the script dynamically adjusts the visibility of the relevant fields.

This approach offers a more robust and flexible method to handle field visibility, accommodating changes in GUIDs without necessitating a reconfiguration of Business Rules.

sample JS code:

function setColumnsVisibility(executionContext)

{

    var formContext = executionContext.getFormContext();

    var lookupAttribute = formContext.getAttribute("lookupAttributeName").getValue();

    if (lookupAttribute != null && lookupAttribute[0].name === "LookupValueName")

    {

        formContext.getControl("firstAttributeName").setVisible(false);

        formContext.getControl("secondAttributeName").setVisible(false);

    }

    else

    {

        formContext.getControl("firstAttributeName").setVisible(true);

        formContext.getControl("secondAttributeName").setVisible(true);

    }

}

Key Takeaway

This experience underscores a critical insight for Dynamics 365 customizations: while Business Rules offer a straightforward method for implementing logic without code, they may not always be the best fit, especially in scenarios involving lookup fields with dynamic GUIDs. In such cases, reverting to JavaScript can provide a more adaptable and reliable solution.