Microsoft Dynamics Course Fees

Business Rules and Their Components in Dynamics 365

Introduction to Business Rules in Dynamics 365

Hello, Dynamics 365 Enthusiasts! 🌟 Today, we’re diving into an exciting topic: Business Rules. Business Rules in Dynamics 365 are like the brain behind your forms. They help automate decisions and enforce logic without the need for complex coding. This feature makes Dynamics 365 user-friendly and adaptable, ensuring that your data is not only captured accurately but also remains consistent across your organization.

Whether you’re a developer, an administrator, or a user, understanding how to create and use business rules effectively will make your work easier and more efficient. Let’s get started!

What Are Business Rules in Dynamics 365?

Business Rules are a powerful way to apply logic to your forms and data in Dynamics 365 without writing JavaScript or plug-ins. They allow you to create conditions and actions that will run on the client-side when users interact with forms. This makes them a go-to solution for real-time validations and data manipulations that enhance user experience.

Example Scenario: Suppose you want to ensure that if the "Budget" field on a form exceeds a certain amount, a "Manager Approval" field becomes mandatory. Business Rules can easily handle this scenario, providing immediate feedback to users.

Purpose of Business Rules

1. Validation: Ensuring that data entered into forms meets certain criteria.
2. Automation: Automatically performing actions based on user inputs, like showing/hiding fields.
3. Guidance: Helping users enter data correctly by providing real-time feedback.
4. Consistency: Applying consistent rules across forms and records, maintaining data integrity.

Components of Business Rules

Business Rules consist of several key components that work together to enforce logic on forms. Understanding each component will help you create effective business rules:

1. Scope:
• Definition: The scope determines where the business rule applies.
• Options:
• Entity: Applies to all forms and server-side processing for that entity.
• All Forms: Applies to all forms of the selected entity but not server-side.
• Specific Form: Applies to a specific form only.
• Example: Setting a business rule for the "Contact" entity to apply across all its forms.
2. Condition:
• Definition: The condition is a logical statement that must be true or false for the business rule action to occur.
• Example: “If ‘Annual Revenue’ > $100,000”.
• Usage: Use conditions to trigger actions, such as showing a field or locking a field based on user input.
3. Action:
• Definition: Actions are what happens when the condition is met. You can add multiple actions for a single condition.
• Types of Actions:
• Show/Hide Fields: Make fields visible or invisible.
• Enable/Disable Fields: Make fields editable or read-only.
• Set Field Value: Automatically set or change the value of a field.
• Set Business Required: Make a field mandatory.
• Lock/Unlock Field: Prevent users from editing a field.
• Show Error Message: Display error messages to users.
• Example: If the "Discount" field value is greater than 20%, show an error message: "Discount exceeds the maximum allowed value."
4. Action Item:
• Definition: Action items are the specific elements like fields or messages that are impacted by the action.
• Example: Specifying the “Approval Status” field as an action item to be set as “required”.
5. Else Condition:
• Definition: Specifies what actions to take when the condition is not met.
• Example: If the condition is not met, reset the “Manager Approval” field to not required.

Hands-On Examples

Exercise 1: Create a Simple Business Rule for Field Validation

Objective: Ensure that the “Estimated Close Date” is not earlier than the “Start Date” on a Project entity form.

1. Navigate to the Form: Open the Dynamics 365 interface and select the Project entity.
2. Open Business Rules: Go to the Business Rules section under Components.
3. Create a New Business Rule: Click on New Business Rule.
4. Set Scope: Set the scope to All Forms.
5. Define Condition:
• Condition: If Estimated Close Date < Start Date.
6. Add Action:
• Show Error Message: “Estimated Close Date cannot be earlier than Start Date.”
7. Save and Activate: Name the rule and save it. Then click on Activate to enforce the rule.

Exercise 2: Automate Field Requirement Based on Budget

Objective: Make the “Manager Approval” field required if the “Budget” exceeds $50,000.

1. Create a New Business Rule: In the Project entity, create a new business rule.
2. Set Scope: Select All Forms.
3. Define Condition:
• Condition: If Budget > 50000.
4. Add Action:
• Set Manager Approval field as business required.
5. Add Else Action:
• If the condition is not met, set the Manager Approval field as not required.
6. Save and Activate: Name it “Manager Approval Based on Budget” and activate the rule.

Exercise 3: Create a Business Rule to Auto-Update a Field

Objective: Automatically set the “Project Status” to “In Progress” when a “Start Date” is provided.

1. Create a New Business Rule: Navigate to the Project entity and create a new rule.
2. Set Scope: Choose All Forms.
3. Define Condition:
• Condition: If Start Date is not empty.
4. Add Action:
• Set Project Status to “In Progress”.
5. Save and Activate: Save the rule as “Auto-Update Project Status” and activate it.

Why Use Business Rules?

1. No-Code Solutions: Perfect for users who want to enforce business logic without diving into coding.
2. Real-Time Feedback: Provides immediate feedback to users, enhancing data accuracy.
3. Consistency Across Records: Ensures that the same business logic is applied consistently across all records, reducing the chance of human error.
4. Ease of Maintenance: Business rules are easy to create, modify, and maintain directly within the Dynamics 365 interface.

Keep experimenting with Business Rules! 🌟 They’re a powerful tool to streamline and automate your business processes in Dynamics 365.

class Runbase_Example extends RunBase
{
TransDate fromDate,toDate;
CustAccount custAccount;

DialogField dlgFromDate,dlgToDate,custDldField;

#define.CurrentVersion(1)
#localmacro.CurrentList
fromDate,toDate
#endmacro
}
protected Object dialog()
{
DialogRunbase dialog;

dialog = super();
dialog = super();
custDldField = dialog.addFieldValue(extendedTypeStr(CustAccount),custAccount);
dlgFromDate = dialog.addFieldValue(extendedTypeStr(TransDate),fromDate);
dlgToDate = dialog.addFieldValue(extendedTypeStr(TransDate),toDate);

return dialog;
}
public boolean getFromDialog()
{
boolean ret;

ret = super();
custAccount = custDldField.value();
fromDate = dlgFromDate.value();
toDate = dlgToDate.value();

return ret;
}
public container pack()
{
return [#CurrentVersion,#CurrentList];
}
public boolean unpack(container packedClass)
{
Version version = RunBase::getVersion(packedClass);
switch (version)
{
case #CurrentVersion:
[version,#CurrentList] = packedClass;
break;
default:
return false;
}
return true;
}
public static void main(Args args)
{
Runbase_Example runb = new Runbase_Example();

if(runb.prompt())
{
runb.run();
}
}

Here I am going to show without using ADAL(active directory authentication library) how to get the authentication token and how to connect to CRM from a standalone HTML Page using the web-API.

I will not explain in detail about how to register an APP in azure and give it access to Dynamics CRM.

Use below code to get the OAuth token once you’re done with Azure app registration

var microsoftTokenUrl = "https://login.microsoftonline.com/4060bfe9-7199-xxxxxxx-xxxxxxx/oauth2/token"; //Add your endpoint URL
var clientId = "xxxxxxxx-9715-xxxx-xxxx-3a1fac0cc5fe"; // Add your app ID
var clientSecret = "xxxxxxMJTQmtu4V73cRyduZ6vS40AlkAtSxxxxxxx";//Add your Secret Key
var resource = "https://xxxxxxx.crm5.dynamics.com";//Add your CRM Url
var grantType = "client_credentials";
function GetAuthroisationToken() {
var token=null;
$.ajax({
url: microsoftTokenUrl,
type: "POST",
contentType: "application/x-www-form-urlencoded",
crossDomain: true,
dataType: "json",
async: false,
data: {
'resource': resource,
'client_id': clientId,
'client_secret': clientSecret,
'grant_type': grantType
},
beforeSend: function (XMLHttpRequest) {
XMLHttpRequest.setRequestHeader("Accept", "application/json");
},
success: function (data, textStatus, xhr) {
token= data.access_token;
},
error: function (xhr, textStatus, errorThrown) {
alert(textStatus);
}});
return token;
}

Here is the sample code to create the lead in CRM (Design your HTML as your wish)

var entity = {};
entity.subject = $("#subject").val();
entity.firstname = $("#fname").val();
entity.lastname = $("#lname").val();
var salutation = $("#title option:selected").val();
entity.address1_postalcode = $("#postalcode").val();
entity.address1_city = $("#city").val();
entity.address1_stateorprovince = $("#state").val();
entity.address1_country = $("#country").val();
entity.address1_line1 = $("#address").val();
entity.emailaddress1 = $("#email").val();
entity.telephone1 = $("#phone").val();
entity.companyname = $("#company").val();
entity.jobtitle = $("#function").val();
entity.leadsourcecode = 8;
var token = GetAuthroisationToken();
if(token!=null)
webApi_Create("leads", entity, false,token);
function webApi_Create(entityName,entityObject,isAsync,token)
{
var newEntityId = null;
$.ajax({
type: "POST",
contentType: "application/json; charset=utf-8",
datatype: "json",
url: resource + "/api/data/v8.2/" + entityName,
data: JSON.stringify(entityObject),
beforeSend: function (XMLHttpRequest) {
XMLHttpRequest.setRequestHeader("OData-MaxVersion", "4.0");
XMLHttpRequest.setRequestHeader("OData-Version", "4.0");
XMLHttpRequest.setRequestHeader("Accept", "application/json");
XMLHttpRequest.setRequestHeader("Authorization", "Bearer " + token);
},
async: isAsync,
success: function (data, textStatus, xhr) {
var uri = xhr.getResponseHeader("OData-EntityId");
var regExp = /\(([^)]+)\)/;
var matches = regExp.exec(uri);
newEntityId = matches[1];
if (newEntityId !== null)
alert("Record Created!");
},
error: function (xhr, textStatus, errorThrown) {
alert(textStatus + " " + errorThrown);
}
});
return newEntityId;
}