web

You’re offline. This is a read only version of the page.

News and Announcements icon

Dynamics 365 CommunityForums Microsoft Dynamics CRM (Archived) Different behaviors of...

Microsoft Dynamics CRM (Archived)

Different behaviors of business rules. Doesn't trigger until record is saved

(0) Share

Report

Report

Posted on by Jorge S

Hi,

I have two business rules, first rule checks if a custom date field has value and second checks if Status Reason has value and it's a specific value.

The different behavior is that first rule is triggered before record is saved and second rule doesn't trigger until the record is saved.

Is this due I'm checking the Status Reason field?

*This post is locked for comments

I have the same question (0)

All responses Img

All responses (3)

Answers Img

Answers (1)

Kumar Viju 1,026 on at

Like (1)

Report

You can check if you have any overlapping Scripts or Business Rules on the Status Reason which is preventing it from triggering before save.

Was this reply helpful? Yes No
Suggested answer

TheMarkChristie 10,328 Moderator on at

Like (1)

Report

Hi Jorge

Your assumption is correct, Can you roll it into 1 rules?

if Field A contact X and Status = Active3 then set Field B to Y and Status to Active4

then put in an else statement for each option?

this would save you doing it as code

Was this reply helpful? Yes No
Verified answer

Jorge S on at

Like (0)

Report

Thanks for your replies. I ended by using JavaScript as I couldn't roll both into one rule

Was this reply helpful? Yes No

Helpful resources

Quick Links

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1

SA-08121319-0 4

#1

Calum MacFarlane 4

#3

Alex Fun Wei Jie 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans