Power Automate Dataverse Adding Scope for Field Changes

3 Comments

In this post, we will look at using the Power Automate Dataverse connector to run only when specified fields change.

In Power Automate, add a new Dataverse connector for Add, Modified, or Deleted. We see the Select Columns:

Now, let’s say we only want this to run when some account fields change, specifically the Number of Employees and the Annual Revenue:

We will add these fields to the select fields:

Let’s run this. We will add another step which we need to save the flow, we will just use a weather step though in practice you would add whatever you need to the flow:

Now, let’s change the Annual Revenue field and save the record:

The flow runs successfully:

Now, lets change the Number of Employees. The flow runs.

Now, if we change any other field, the flow does not run, and you will not see a Succeeded record.

Note, the output fields are not limited to the filtered fields:

 

THANKS FOR READING. BEFORE YOU LEAVE, I NEED YOUR HELP.
 

I AM SPENDING MORE TIME THESE DAYS CREATING YOUTUBE VIDEOS TO HELP PEOPLE LEARN THE MICROSOFT POWER PLATFORM.

IF YOU WOULD LIKE TO SEE HOW I BUILD APPS, OR FIND SOMETHING USEFUL READING MY BLOG, I WOULD REALLY APPRECIATE YOU SUBSCRIBING TO MY YOUTUBE CHANNEL.

THANK YOU, AND LET'S KEEP LEARNING TOGETHER.

CARL

https://www.youtube.com/carldesouza

 

ABOUT CARL DE SOUZA

Carl de Souza is a developer and architect focusing on Microsoft Dynamics 365, Power BI, Azure, and AI.

carldesouza.comLinkedIn Twitter | YouTube

 

3 Responses to Power Automate Dataverse Adding Scope for Field Changes

  1. Hello Carl,
    I am currently implementing your suggestion.
    However when I enter the column name of a lookup column in the ‘select columns’ area the flow won’t trigger with the following notification:
    There’s a problem with the flow’s trigger. Fix the trigger, Learn more
    The following filtering attributes are not valid in entity TableName: LookupColumnName

    made a topic on https://powerusers.microsoft.com/t5/Building-Flows/When-a-Row-is-modified-Dataverse/m-p/2306490#M256519 about it.
    If you have any suggestions?

  2. Hi Carl!
    If I understand correctly, your solution is only for changes around a limited number of columns. What I’m looking for is how to log changes for most of the columns and getting exact changes. That would require building a separate flow for each column changes of which I need to track. I’m not happy about that, because that would be a lot of such flows. If only I could get the information form the trigger, what column was changed and what was the value input in that column, that would suit my needs.
    Any ideas how to do it instead of creating separate flows for every column?
    Best regards
    Peter

  3. From what I’ve seen, this works only for a limited amount of fields. For instance, if i wanted the flow to run only on 30 fields, its breaks. Seems like the limit is around 11 fields according to my tests. Is there a way to allow a flow to trigger on 30 fields? Or even better, mention the fields that we do not want them to trigger a flow?

    Thank you!

Leave a Reply

Your email address will not be published. Required fields are marked *