Unanswered

Dataverse trigger flows when a row changes - column filter bug

(3) Share

Report

Posted on by rw_ga

137

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."

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"?
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!
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!

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?
Allow Triggers to use any data from a row. Null and empty are values for optional columns/fields!
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

Categories:

Building flows

I have the same question (0)

All responses (42)

Answers (1)

Mira Ghaly 11,413 Moderator on at

Like (0)

Report

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.

Was this reply helpful? Yes No
rw_ga 137 on at

Like (0)

Report

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).

Was this reply helpful? Yes No
Mira Ghaly 11,413 Moderator on at

Like (0)

Report

@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?

Was this reply helpful? Yes No
Big Kahuna 42 on at

Like (0)

Report

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).

Was this reply helpful? Yes No
Mira Ghaly 11,413 Moderator on at

Like (0)

Report

@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?

Was this reply helpful? Yes No
Mira Ghaly 11,413 Moderator on at

Like (0)

Report

@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

Was this reply helpful? Yes No
Big Kahuna 42 on at

Like (0)

Report

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?

Was this reply helpful? Yes No
Big Kahuna 42 on at

Like (0)

Report

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

Was this reply helpful? Yes No
Mira Ghaly 11,413 Moderator on at

Like (0)

Report

@Iddy

Yes parentcustomerid is a lookup.

Was this reply helpful? Yes No
rw_ga 137 on at

Like (1)

Report

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?

Was this reply helpful? Yes No