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

[rw_ga]

Well I'm back, This "Select columns" option in the flow trigger is bugging out again!  Now I have flows triggering even though the data changed is in a column NOT LISTED!!!!  What the heck...  For me this is a major issue, I have 3 different "modified" flow triggers using the select column option to fine tune WHEN to actually trigger.  They each do different things when the different columns get changed.  All of the sudden I now have all 3 flows triggering EVERY time ANY data is changed on the row! 2 of the flows call the same child flow which in turn creates a row in anther table which is now creating multiple rows!

Waiting on MS support to respond.  I'll try to provide feedback here if/when its resolved.

[rw_ga]

Update:  Spoke with a support rep.  I think we have narrowed down what is happening, but not sure how to address it.  My ticket is being transferred to another team.

Notes: 

• I enabled auditing on the entity/table to see which fields/columns are "Showing" as being modified. 
  • There is only one listed in the audit with a change.
• I can manually edit the record/row to change the same value listed in the audit and it doesn't trigger all the flows.  Manual edited using browser and model-driven app.  INTERESTING!!!
• I go back to the child record/row that has a flow monitoring changes and updates this parent record.  In that update action for this parent record, it has multiple fields LISTED to be updated.  Seeing that they don't "always" change, then there shouldn't be an change if the value is the same. 
  • AND HERE IS where I think the issue lies.  Even though Dynamics doesn't see or record the change in the audit, the FLOW triggers because a value has been passed in the update action.

So, how do I configure it so that it only triggers when the values CHANGE in the table and not just by passing the same ones already there?

[rw_ga]

Does anyone know how to use the "if" expression to only pass a value when one is present, otherwise don't pass anything?  I tried: 

if(equals(outputs('Get_a_row_by_ID')?['body/number'],variables('Number')),'',variables('Number'))

My hope was that if the values were equal, then pass nothing = '', but if false, pass the value to update.

But that isn't working.  '' evaluates as a string and I'm afraid if I use the Null expression, it will just clear the field on the parent record. 

[rw_ga]

Just posting an update in case anyone else runs across this:

So I tried using multiple variations of the if expression to 'not do anything' and it doesn't appear that its an option.  Not that it will now, but using '' might clear a string value so that's not a good idea and we can't just leave the if true or false value blank.  Expression isn't valid anymore....

If it hasn't already been requested, then I'm going to locate the feature request site and post my request there.  I've run into a couple scenarios now that "doing nothing" would have saved me a lot of conditional branches in my flows.  Think polymorphic lookups NOW, we are presented with multiple columns instead of just one column like in the old days when you didn't have to specify the /tableinfo(guid) formatting.

[rw_ga]

Created a new flow today and experiencing the issue AGAIN!  "Lookup column not triggering cloud flow."  Note:  I also noticed lookup column change isn't being recorded in audit. 

I opened a case with MS.  Got routed to Power Automate support since I thought it was a flow issue but they said I needed to be routed to another team, Dynamics.  Microsoft recommends using Microsoft Power Automate for automating workflows, BUT you can't get to the correct support team when an issue with Dynamics and Power Automate crops up!  You have to TRY one or the other and then they determine if they can help...  Very frustrating...  

[rw_ga]

There must be something weird (delay) with using lookup columns in the column filter.  Not sure why, but this new flow is now triggering correctly.  This seems to be what happened last time. 

I created the flow, tested it and it didn't work.  I researched the issue, posted about it here, then tested it again after a few minutes it appears to start working.  Today I created the flow, tested it and it didn't work.   I created a MS support ticket, MS Support called me and we tested it while on the phone and it didn't work.  MS Support thought it was an issue with Dynamics and is supposed to be rerouting the ticket.  I just went back to test it again and now it appears to be working. 

????

[SK7]

Once it begins to work, does it continue to work?

[NirSeagas]

hey all,

i was facing the same issue where i cant trigger the flow using dataverse 'when a row is added or modified' by lookup at the filter rows(at the select columns its work but of course we want to be more accurate so using filter rows for specificed condition needed). 

the solution i found is that you need to go -> component setting and add trigger condition like this : 

*works also for name

[rw_ga]

Hi SK7,

I want to say yes, but don't know of a good way to really monitor flows. If they aren't, WELL, I guess we have some data issue in our system then because something didn't get updated like the flow was designed to do....

This low code approach has become difficult to work with at times!  It is great that they are improving it, but there are times when it appears changes may not always benefit us low coders!  

[Anonymous]

@Mira_Ghaly  I was wondering if you may have some insight into my scenerio.  In addition to my flow being triggered if specific fields in dataverse are updated,  I am looking to create an entry for each of the field changes.  

For example, Contact A's  Job Title, Department, and Last Name were updated, so in my related table 3 rows are created for each of the fields that were updated, each would also need to indicate the field that was updated.  

Are multiple flows needed- one for each field change?

Ideally, this would be handled in a single flow, but trying to figure out how to achieve this.  Any help would be so appreciated.

[Mira_Ghaly]

@Anonymous 

Why would you do this if you can use the Out of the Box Auditing feature which does the same for you..

Please have a look at it here:

https://docs.microsoft.com/en-us/powerapps/developer/data-platform/auditing-overview

https://docs.microsoft.com/en-us/powerapps/developer/data-platform/configure-entities-attributes-auditing

[shavora]

Not sure it's helpful to anyone else but lookup columns in dataverse for custom entities I have to write the name in the Odata filter in a special way. If logical name is crf_lookupname it would be _crf_lookupname_value. I test this by looking at the raw output in either the trigger or List row action to find the correct naming for lookup fields.

[rw_ga]

@shavora,

Here are a few tools/tricks I find useful when working with cloud flows and MS Dataverse.

• The "Level up for Dynamics 365/Power Apps" chrome extension.  I'm not affiliated with them in any way.  I just use the extension.  Anyway, you navigate to the model-driven app form on the frontend (with the fields you want to work with) > Click on the plugin icon in the browser > Click "All Fields" in the list.  A new tab opens showing all the fields, even the hidden ones end users don't normally see.  It has other great options like Show Optionset Values, that way I don't have to launch XrmToolBox to get to FetchXML Builder.  CORRECTION - Sorry, I like the "Show Optionset Values" option, I DON'T USE FetchXML to get Optionset values.
• Speaking of XrmToolBox, if you don't have that one, grab it too.  FetchXML Builder made life so much easier when needing to return somewhat complex data in the "List Rows" actions.  If it gets too complex, it may not show up in the "Dynamics Data" view.  For those you can try to add a "Parse JSON" to get the data to be accessible via the Dynamic Data.  Polymorphic Lookup Manager and Ribbon Workbench are also on my Start page under Recently Used Tools in XrmToolBox.
• Just need to get to the 'text' value of a field so that you can use it in an expression, add it by selecting the entry in the dynamic data first, click the added field once to highlight, then press CTRL + C to copy it.  Remove it, click on the expressions tab, hit CTRL + V to paste, and finally remove the surrounding @{}​ which I think is used to display it visually, see example below
  • 
  • @{variables('hostName')} = variables('hostName')

Happy automating!

[carterbarry88]

I just had the same issue where both lookups and option sets were not being accepted in the trigger.

What resolved the issue for me was removing the space between the columns. I had multiple columns.

What didn't work:

 column1, column2lookup (with the space between)

What did work

column1,column2lookup (with no space)

Hope that helps someone

[ct_klein]

Are folks still having this issue?

I have a optionset in CRM on the Plans entity.  I wanted to continue the flow if, and only if, the ct_servicetype was changed.  It works fine as far as evaluating the value of ct_servicetype, however if I make any changes to any other field on the Plan and save it the flow is triggered.

Has anyone found a permanent solution to this?

[rw_ga]

@ct_klein 

Its been a hit or miss for me when working with columns other than the basic text columns.  Check the column name spelling, make sure no spaces are before or after the column name, and also give it some time after saving to see if it works properly.  It appears to me that sometimes there is a delay on the backend that doesn't immediately recognize column filtering settings.  Maybe not, but I don't have any other explanation of why sometimes it just starts working after leaving it alone and looking across the internet to see if there are other possible solutions to the issue.

[Youcef]

Hi All,

I have the same issue but on a Yes/No field. As a matter of fact I would like my flow to trigger whenever this Yes/No field changes.

I tried putting the logical name of my field in the columns of the trigger definition but the flow does not trigger.

Very best regards.

Youcef

[Stevieed]

not gonna lie after 2 years this issue is still on going, these MS tech people are just bunch of idiots

[Vitss]

Encountering the same issues: topic any help would be usefull.

[AABBBCC]

the solution is quite simply after hours retrying:

Don't use the "Display name" of your column, 

Don't use the "Schema name" of your column,

Do use the "Logical name" of your column.

see this screenshot attached.