web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

Business Rules Do Not Apply to Default Value

(0) ShareShare
ReportReport
Posted on by 455

I have a customized phone call activity with a related business process flow, and I have business rules that set the visibility of other fields based on fields before it.  One of the fields is a two option field (yes/no) with a default of no, and the business rule makes the fields invisible if the field is set to no.  This means the fields should be set to not visible when the form first loads, but this is not the case.  If I set the field to Yes, and then back to No, the rule executes and the fields are made invisible, but this does not help me when the form loads.

I thought to just set the fields to invisible by default, which works for the form, but the fields are still visible in the Business Process flow.

Is there any way to work around this through configuration?  I hate to add javascript to execute what I have the business rules set to do.

Also, this is obviously a bug.  The business rule should execute on form load based on the field defaults.  I also think fields that are not visible should not show in the business process, but I could see how this could go either way.  How do I report bugs in CRM to Microsoft?

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Rasmus R. Aardal Profile Picture
    on at

    Hi John,

    It seems process flows only fire onLoad for the process phase that is active when the form is loaded. I haven't been able to find a workaround for hiding fields in other process phases without using onChange as a trigger.

    I do not think you can choose to hide fields in a process by default. To work around this, however, you can set up a business rule that has the criteria:

    "If Phone Number (Or some other field on the main form that always has content) Contains Data, then:

    Hide Field [Name of field in current process phase you wish to hide by default]

    It is clearly a crude workaround, but I hope it helps you until the business rule functionality is extended to cover your needs :)

     

    Regards,

    Rasmus

  • Suggested answer
    John E. Bailey Profile Picture
    455 on at

    You are right, the issue is with the Business Process Flow and not the business rules.  The future stages in the business process flow do not change based on the business rules.  You can actually have different values displayed on the form verses the business process flow.

    Your suggestion put me on the right track, but it is missing an important detail to work.  The business rules only fire when their fields change.  To make the rule work, you also need a synchronous workflow that changes the field in question every time the stage changes.  So basically you add a trigger based on a field containing data, and then in a synchronous workflow, you change this field every time the process stage changes.

    I agree, this is a crude workaround.  I would also consider this a bug in the system, so my question regarding how to report bugs in CRM is still a valid one.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
JS-09031509-0 Profile Picture

JS-09031509-0 3

#2
AS-17030037-0 Profile Picture

AS-17030037-0 2

#2
Mark Eckert Profile Picture

Mark Eckert 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans