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
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.
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.
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.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,240 Super User 2024 Season 2
Martin Dráb 230,149 Most Valuable Professional
nmaenpaa 101,156