Dataverse trigger flows when a row changes - column filter bug

[rw_ga]

Trigger flows when a row is added, modified, or deleted - Power Automate | Microsoft Docs states "Use the Column filter box to define a set of comma-separated, unique names for the table, as shown in the following image. The flow runs only when these columns change on the specific rows." 

1. I find this statement a little confusing, does this phase "unique names for the table" try to tell us to use the "unique name of each column"?
2. This doesn't work for all column/field types.  So filtering columns isn't accurate.  It should either filter by ANY column/field type or be changed to say "A distinct set of columns/field types that can be filtered but you will have to guess which ones... hehehe" so that its more accurate!
3. If it does allow adding lookup columns to the column filter area, what name do I need to use?  BECAUSE THE UNIQUE NAME FOR THE LOOKUP DOESN'T TRIGGER THE FLOW!

Trying to be a citizen developer is so frustrating when MS doesn't support their own column/field types and returned data in triggers and actions!

1. Please ADD your hidden fields you/MS use on forms and other areas to the Dynamic Data.  You use this information why can't we?
2. Allow Triggers to use any data from a row.  Null and empty are values for optional columns/fields!
3. Allow Saving flows with errors, we may need to run out and have to get back to the flow later and to lose everything because one issue cropped up while building the flow throws an error shouldn't require us to fix it before we save it!

• Example a lookup field appears to use 4 fields/values (and the column name/schema name doesn't appear to even be used):
  • Microsoft.Dynamics.CRM.lookuplogicalname
  • Microsoft.Dynamics.CRM.associatednavigationproperty
  • Microsoft.Dynamics.CRM.lookuplogicalname
  • _columnname_value

[cheesylobster]

Guys, I ran into the same thing and was stuck for a good while even if I used the correct logical name. What fixed it for me was setting the Run as to flow owner in the when modified trigger. I did not try other options since that one works for me. Hope it helps! Please see my answer 😢 I know how much it sucks couldn't get that working.

[PJT1]

Has there been any actual documentation about how to use lookup fields in the "Select columns" section of the trigger? The answers I'm seeing about the whole "logicalname" are not working/not the solution.

My flow never triggers and just times out when I use that field as the only triggering field. I have auditing enabled on it, so I KNOW it changes. It also works when I add modifiedon as a Selected column. Unfortunately, cheesylobster's suggestion of using the Run as Flow Owner is not working for me, since I've been using that option since I created the flow.

[PJT1]

It literally started working after I posted this. RIGHT after. I didn't change anything between making my above post, and trying it again.

The only thing that changed was that I asked my coworker to try, he built a super simple flow using my exact trigger setup, and it worked for him. I tried his flow after finishing the above post, it worked, so I went back to my flow and it worked.

Like, it's great that it works, but why is it SO inconsistent? It's unreliable and difficult to test.