power automate and dataverse

[linadeveloping]

hi everyone, I tried everything but the result comes back false, i have done everything right as you can see its simple and straightforward?? and idea why?

[a33ik]

Hello,

It's a bit hard to give you an answer without seeing what data you query and what's the condition.

[linadeveloping]

Hi, i am trying to use a dataverse custom table choice field as a trigger based on the status change 

[a33ik]

As I mentioned, screenshots will help. Please, provide it.

[ivan_apps]

So we need to see more info from 2 places:

• what is your filter condition in the Dataverse trigger? Since it executed correctly I assume you have the right syntax but it’s helpful to know what you’re triggering on.
• Your condition statement criteria needs to be shared. This evaluates to false but we have no idea what the condition you are evaluating is. What are you checking before you send an email?

note that often times you can use the row level filtering or the column level filtering on the trigger to only trigger your flows when a column equals a specific value, so you may be able to remove your ‘condition’ entirely depending on your requirements for this.

[Jondoesflow]

This post might help

https://www.jondoesflow.com/amp/filter-array-ftw

---------------------------------------------------------------------------


If I have helped you with an answer, please accept this post as a solution and thumbs up my reply. Thanks !

Blog - JonDoesFlow
Twitter - JonDoesFlow
YouTube - JonDoesFlow

[ivan_apps]

So… still would be good to know field names and the actual conditions that you are checking but here’s my best guess: 

- if the status on table X changes, fire an email.

First, I would change your trigger to when a row is modified unless a creation email is desired.  Deletion has separate implications, you might want a separate flow for that.

In Advanced Settings for your trigger define the following:

Filter Rows: statusreason

Filter Expression: statusreason eq ‘[status reason id number you’re trying to send an email on]’

you can then delete your ‘condition’ step and simply send the email. It will only fire off when the status changes to a specified value, so no other checks are required.

note that if you’re coming from a SharePoint trigger background, Dataverse is much more capable when defining specific field triggers, so you don’t have to fire flow on every change and check your specific field for a value, define it as part of the trigger instead.

Link to docs:

https://learn.microsoft.com/en-us/power-automate/dataverse/create-update-delete-trigger?tabs=classic...