You’re offline. This is a read only version of the page.
24
Hi,
I want to create a flow that is only triggered when an record is updated (CDS Update) and the update is done on a specific field and value.
When only using the filtering attribute, the trigger is working as expected: when the field is updated, the flow runs. But when also adding the filter expression on the same field but with a value specified, the flow is not triggered.
Another test where only the filter expression is put in is also working, the flow runs only when the specific value is present but it runs for all updates done on the record regardless which field is updated.
So it looks that it's not possible to use both the filter attribute and expression on the same field??
Anyone else experiencing the same problem and having a solution?
Regards,
René
Hi John,
Both scenarios were tested.
But I have to recall my previous reply at the point that only using a filter expression is sufficient. It's not!
When you want to have a flow triggered on an update of one particular field having a specific value, you'll have to add the attribute and the filter expression.
If only the filter expression is put in, any update on that record will trigger the flow if also the expression is (remains) true.
Still, the strange behavior during testing remains. Only when stopping the flow, doing edits and starting again, does give the correct results in the end.
Regards,
René
Hello @RenevM
I have never worked with CDS, but I need some clarification on the tests you performed. Did you try the below using both filtering options:
What was the result of the above?
Kind regards, John
#1
WarrenBelz
146,535
Most Valuable Professional
#2
RandyHayes
76,287
Super User 2024 Season 1
#3
Pstork1
65,908
Most Valuable Professional
Share
Report
All responses (
Answers (
