Looking for PowerObjects? Don’t worry, you’re in the right place! We’ve been part of HCL for several years, and we’ve now taken the final step in our acquisition journey: moving our website to the HCL domain. Nothing else is changing – we are still fanatically focused on Microsoft Business Applications!

PowerObjects Blog 

for Microsoft Business Applications


Setting Field Values vs. Setting Default Values in Business Rules

Post Author: Joe D365 |

Business Rules for Dynamics CRM (sometimes called Portable Business Logic or PBL) can be used to create rules at an Entity level. For this example we will discuss the difference between setting a field value in a business value vs. setting a default value. To begin, a business rule needs to be added. Follow the steps below:

1. To add a business rule, navigate to the form of the entity to which you would like to apply the rule.

Setting Field Value vs. Setting Default Value in Business Rules

2. Select Business Rules and click the New Business Rule button as you normally would to create a business rule.

 

Setting Field Value vs. Setting Default Value in Business Rules

3. Using business rules (PBL) you now have the option to set a default value. Setting a default value should be used when you want a field to appear with a set value on load. Being able to set a default value is a standard feature for option sets. Using the PBL Set default value feature allows you to set default values for numeric, text, and lookup fields as well. Set your condition and under actions select Set default value.

Setting Field Value vs. Setting Default Value in Business Rules

4. When you select default value you will be able select the field, type, and value to be input under the ACTION section. Here the default value for the credit limit field is being set to $10,000.

 

Setting Field Value vs. Setting Default Value in Business Rules

 

5. Now, for every new account that is created, $10,000.00 will be the starting value for the credit limit field on the form.

Setting Field Value vs. Setting Default Value in Business Rules

 

Business rules (PBL) also allow you to use the Set field value. This should be used when you want to apply logic and don't need to have a field set on the form load. For example under the company profile section, logic might be needed to fill in a field saying if a SIC Cod begins with 0 set the Industry field to Agriculture and the ownership to Private. This can be done using the following steps with Set field value:

1. Set the condition that is required for the field value to be set and under the ACTION section, select Set field value.

Setting Field Value vs. Setting Default Value in Business Rules

2. When you select set field value you will be able select the field, type, and value to be input under the ACTION section. Here the field values for Industry and Ownership are being set

Setting Field Value vs. Setting Default Value in Business Rules

3. When this is activated, within the account form, when the condition is met, here being an SIC code entered beginning with a zero and saved, the Industry and Ownership fields will be populated.

Setting Field Value vs. Setting Default Value in Business Rules

That is the difference between using Set default value and Set field value in business rules! For more on business rule you can visit our main PowerObjects Dynamics CRM blog, or check out a few individual business process flow related blogs below:

Happy CRM'ing!

 

Joe CRM
By Joe D365
Joe D365 is a Microsoft Dynamics 365 superhero who runs on pure Dynamics adrenaline. As the face of PowerObjects, Joe D365’s mission is to reveal innovative ways to use Dynamics 365 and bring the application to more businesses and organizations around the world.

3 comments on “Setting Field Values vs. Setting Default Values in Business Rules”

  1. Hi JoeCRM,

    Thanks for this detailed explanation and this is a really powerfull addition provided by Microsoft!

    My concern is about de set default value on lookups. These are records in de database and links probably are broken when you import the solution cross organization (OTAP principle) because of different GUID's?
    The reason why I think about this is because I worked a lot with business units, teams, queues etc. I have also written code to set default (active) pricelist to make sure the code / pricelist is not hard coded and doesn't work cross environment. Because all entities mentioned above are records in the database and linked based on their unique GUID. When exporting customizations, teams etc. these links are broken because their GUID is different over all organization.

    What do you think? Look forward hearing from you.

  2. Hi JoeCRM,

    I have a question about fields.

    Is there a way to resize fields to make them display a larger amount of text?

    I have been struggling with this for a while now, and I simply can't find the place where the field size can be edited.

    Any ideas?

    Thanks!

  3. I tried to set up default value for Potential Customer(customerid) lookup on Opportunity form but that field itself is not available in Business Rules window. Any thoughts?

PowerObjects Recommends