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 :
Customer experience | Sales, Customer Insights,...
Answered

Trigger Workflow on two Option field Dynamics CRM CE

(0) ShareShare
ReportReport
Posted on by 299

Hi there,

I have a two option field on contact.

based on the client selection, for example 'Yes', a workflow gets triggered ,it checks the condition and creates a case.

On the selection of 'No' it creates some other case, the default of this field is 'No' , so somehow nothing will change and the workflow will not get triggered.

so have should we trigger a workflow on the default value of the two option field.

Regards.

Sam

I have the same question (0)
  • Verified answer
    Carlos Eduardo Fontolan Profile Picture
    on at

    Hello, 

    I hope you are doing well. 

    The workflow trigger field that has changed information and probably this field wasn't dirty when default value is set.

    You can check if field was changed using 'getIsDirty' through javascript based on official documentation https://docs.microsoft.com/en-us/powerapps/developer/model-driven-apps/clientapi/reference/attributes/getisdirty

    If the field isn't changed you can use 'setSubmitMode' also through based on this official documentation https://docs.microsoft.com/en-us/powerapps/developer/model-driven-apps/clientapi/reference/attributes/setsubmitmode to indicate that this field needs to 'update', even with same value.

    Or you can change your workflow to trigger using another field and validate this field on condition. 

  • Suggested answer
    Community Member Profile Picture
    on at

    Hi,

    My Opinion is to change this field to "OptionSet" type, then you can put the default value = null

    after that, when you change the field value , the workflow will triggered.

  • z.sam Profile Picture
    299 on at

    Thanks for your reply Carlos,

    'getIsDirty' idea was great, but I wont be able to use it as a trigger field on my workflow.

    I have another field on the 'No' value of the option set I will use that.

    Regards.

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!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
11manish Profile Picture

11manish 165

#2
ManoVerse Profile Picture

ManoVerse 156 Super User 2026 Season 1

#3
Zhilan Profile Picture

Zhilan 49

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans