Unanswered

How to use Dataverse trigger Add, Update Delete Row for image columns?

(0) Share

Report

Posted on by Community Power Pla...

Hi everyone, we have a flow that should be triggered when some dataverse image columns are changed. But checking the runs of the flow it seems like the trigger fies too frequently for image columns and sometimes without a reson. Does anybody know why this thing is happening or how i get the trigger event when an image column is modified Kind regards

Categories:

Using flows

I have the same question (0)

All responses (4)

Answers (0)

AnthonyAmador 2,553 Moderator on at

Like (0)

Report

Hi @Anonymous

It looks like you can select the column you want to trigger the flow in the advanced options.

Hope this helps.
Cheers.
If my solution helps, then please consider Accept it as the solution to help the other members find it more quickly.

Was this reply helpful? Yes No
Community Power Pla... on at

Like (1)

Report

Thanks @AnthonyAmador for your answer,but it seems this is not the case for image columns because they are treated differently from "normal" columns in dataverse. We are using anyway the select columns and filter rows options due to high volume of records but the trigger and the flow are triggered for records that haven't been update manually or from some other process of powerplatform flows
Kind regards

Was this reply helpful? Yes No
Gyllentid 894 on at

Like (0)

Report

My flows are also triggered when nobody is even online to do anything with the table, so I am wondering this as well. Hoping to understand this more!

Was this reply helpful? Yes No
Community Power Pla... on at

Like (1)

Report

Hi @shavora ,
we solved it with a workaround, if it interests you. We added a new bit 0/1 column for every photo column. We called it ModifiedByFlowPhoto1, ModifiedByFlowPhoto2 etc. With a business rule in the table, every time a photo is uploaded from user we do the corresponding field eq 1. We changed the powerautomate flow to run based on recurrence, and then we put a filter in the records if these fields eq 1. With this approach the flow gets only the manually changed records, when the flow ends we update the record to eq 0 so the flow wont pick it again, otherwise if we kept the on add/update/delete trigger powerplatform triggers millions of runs that neverend
Regards

Was this reply helpful? Yes No