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

[Mira_Ghaly]

Hi @rw_ga 

Yes the documentation is a bit confusing, for the lookup Issue you are facing I made a test and it is  working on my side.

Can you share some details and we may figure it out, also make sure there is not spaces in between the columns.

[rw_ga]

Hi Mira_Ghaly,

The trigger "Change type" is set to "Modified" and the "Column filter" only has the unique name of the lookup column (example: new_lookupcolumnname).  The flow doesn't trigger.

If I don't specify anything in the "Column filter" the flow will trigger when the lookup column changes.  I suspect it's triggering because the row's modified on and modified by are also getting updated when the lookup is changed and saved, then those fields trigger the flow!

So.... How do you use the column filter option to specify the lookup column? (I'm wanting only a select few columns to trigger this flow and one of them is a lookup).

[Mira_Ghaly]

@rw_ga 

Can you please share a screen shot of your column filter because i tried and it is working on my side so screenshot can help either reproduce your issue or identify what might be the issue?

[Iddy]

I've been trying this too.

From my research it seems to work for simple columns (you need the fully qualified column name with your solution prefix if you app is coming out of a solution), however it does not trigger if you try and add a lookup column to the list of column filters.

Nor do any of the other previously working columns.

Unless someone knows some magic here for referencing the lookup column in the column filter I'd say its a bug or omission by design (please update the docs).

[Mira_Ghaly]

@Iddy 

So you mean when you add a lookup column among other types of columns?

Can you tell me please what other column types so I can try to reproduce?

[Mira_Ghaly]

@Iddy @rw_ga 

This is what I am trying at my side and it is working for any of the 3 fields

I will try on custom entities and custom fields as well but it would be great if you guys share with me some more details so I am able to reproduce it

[Iddy]

Here's what I tested. Add the name field (my solution is prefixed stk_ so I added stk_name). Tested the workflow (manual test in the browser). This works fine - updates to the record do not trigger the flow unless the name field is changed.

I have a second field on my entity, exam (named stk_exam). Its a lookup field to a second custom entity (Certification Exam). If I add it as a filter (as the only filter) the workflow does not trigger, I've tried various combinations (exam, stk_exam, stk_exam_value). Also, if I add it to the end of the list of columns (i.e with my name filter as well) the workflow no longer triggers on the update to the name field. I am wondering if the field needs to be refenced differently?

[Iddy]

Are any of those lookup fields? My flows trigger for simple columns.

[Mira_Ghaly]

@Iddy

Yes parentcustomerid is a lookup.

[rw_ga]

Hi Mira_Ghaly/Iddy,

Thank you both for providing your experiences. I'm getting mixed results and don't know why other than its some type of BUG or I need to do something different with custom tables/lookups!

Recap: 

I'm using Dynamics 365 for Sales Ent. (Online).

I created a "unmanaged solution" to hold all my custom STUFF.

I created multiple custom tables (they are the standard ones not Activity Type)

I created cloud flows to trigger when rows in these custom tables get modified (specific columns using column filter).

In testing:

Using OOB Account, Parent Account Lookup (parentaccountid) with the column filter triggers the flow.

Records:

Column Name:

Flow:

Select Test 1 in Lookup field:

Flow Run History:

Using custom tables/lookup columns with the column filter doesn't trigger the flow.

I use the same process with custom tables and lookups and it won't trigger!  What the heck!!!!  Why doesn't it work the same for custom tables and their lookups?

[rw_ga]

Well, I'm at a complete lose.  I just tried it again this morning and it APPEARS to be working for me now.

@Iddy, 

I tried it before and it didn't appear to work, but I'm currently using just the "Name" of the column that is displayed when viewing all columns of a table. NOTE: I did notice a red banner after saving the cloud flow that indicated something was wrong with my trigger like before, but this time it worked and that went away after I changed a record (lookup column value) and it triggered the flow. 

WORKED:

• new_lookupcolumn

DOESN'T WORK:

• new_lookupcolumn@Microsoft.Dynamics.CRM.lookuplogicalname
• new_lookupcolumn@Microsoft.Dynamics.CRM.associatednavigationproperty
• new_lookupcolumn@Microsoft.Dynamics.CRM.lookuplogicalname
• _new_lookupcolumn_value

Did somebody change something on the backend!  Someone is just messing with me!!!

[rw_ga]

Okay, whoever fixed the lookup field, can you fix the image field type now?  The trigger only appears to fire when you remove the image and not when one is added!

Still a "Column filter" issue/bug, doesn't work the same for all column types.  Now I only have an image column I want to monitor.  I can add an image and it doesn't fire but it will fire when the image is removed.  I need it to fire when an image is added too!

Thanks

[rw_ga]

I noticed there are a few image column (field/values) MS uses but doesn't really tell us about:

For Example, if you create an image column named "Image", it defaults the NAME to something like "new_image".  But using a Chrome browser extension like "Level up for Dynamics 365/Power Apps" Offered by: Natraj Yegnaraman you can see the following other fields are present.  So similar to a lookup, it appears there might be multiple values used with an image column and probably the file column too.  Now the next question is when can we use these with triggers and actions...  MS doesn't appear to support all of them everywhere.

• new_image
• new_imageid
• new_image_url
• new_image_timestamp@OData.Community.Display.V1.FormattedValue
• new_image_timestamp

As a workaround and until the image column type gets fully supported/fixed in the column filter, I've added both:  new_image,new_imageid which triggers the flow when an image is added OR removed!  

Again, its so frustrating that we have to search for odd workarounds when MS should just support all their own fields at both the trigger and action levels!  Why are there these hit or miss attempts???  By the way, that new_imageid appears in the Dynamic data tool when I searched for image!!!!  Go figure....  I can't get a label or the displayed text of an optionset or lookup from the Dynamic data but I can get this imageid....

Hope this helps someone else fighting to use these tools.  Don't get me wrong, the whole concept of allowing citizen developers is great!  I just wish it executed a little cleaner.

[Mira_Ghaly]

@rw_ga

I did a test using a custom table and custom lookup and it fired OK as well and I think now the lookup is working fine with you but you have an issue with the image / file column types which you have successfully found a work around.. Is my understanding correct?

[rw_ga]

Edit: Yes it does appear to be working with the lookup Name in the column filter option.

I did find a work around for the image column, but don't know how long it will be supported (if it's supported at all).  Hopefully that issue will get fixed as well!

[Iddy]

So, this flow is now working, using the solution qualified name of my lookup field (stk_exam). The same option I tried unsuccessfully yesterday. I have no sensible explanation for this. 

[rw_ga · Accepted solution]

@Iddy,

I think someone fixed something on the backend, because I had the same experience!

[Anonymous]

Hi Mira_Ghaly,

I have a question, in the below Column filter... which is now "select columns"

Can I Give multiple columns with or condition.

I have a requirement where I want to Update a record when there is Row  Modified with any one of the selected  Columns.(Like dirty fields).

Any help would be so greatful.

Thank you

[Mira_Ghaly]

@Anonymous 

The purpose of the column filter or Select Column is that these are used as triggers to your flow , so when either of these columns change your flow gets triggered.