PowerApps Flow with trigger not showing updated data on modify

(1) Share

Report

Posted on by DB-22041341-0

I have a flow with When item is created or modified, with a trigger condition @equals(triggerBody()?['NotifyICAndICTEmail'], false). The NotifyICAndICTEmail is a yes/no in a SharePoint list with no as a default. I run through the flow which is just sending an email and then updating the NotifyICAndICTEmail to True. On any update to the record It skips the trigger condition all the time because the field is always false. Not matter how many runs I do, updating data, run again, SharePoint list is showing the NotifyICAndICTEmail is True, but the field in the output is showing as False. I have tried to put a Get Items after the trigger and it still is showing as false coming back with the data. The only thing that I can see that the data changed is when I use Get changed for an item or a file (properties only), I can see Has the field changed is True. How can I make sure the beginning trigger is pulling new data and not cached data?

Categories:

Building flows

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Vish WR 3,748 on at

Like
a
(0)

Report
Copy link

Link copied!

@DB-22041341-0

Can you try the condition in flow instead of trigger

Was this reply helpful? Yes No
DB-22041341-0 25 on at

Like
a
(0)

Report
Copy link

Link copied!

I have tried the condition in an If, but the problem is the value doesn't change to True even though the SharePoint list is updated and the it is checked. No matter what I do the NotifyICAndICTEmail reads as False. I have used the Get items, and still do not get the latest values. So my flow will always tell me I am in an infinite loop and it will run all the time. Makes no sense to me that this does not get a new instance of the row data, but that is what appears to be happening. And if there are users in there during the day, there will be multiple runs of this this flow because of that reason. But this morning I ran a test on the same record being updated and the flow did not run, I can only assume it is picking up the correct instance of the row. So the problem is when the record will be worked on multiple times in the same day and time period. Maybe longer delay????

Was this reply helpful? Yes No
Suggested answer

sumit_artesian 261 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @DB-22041341-0,

The fact that “Get changes for an item” detects the update tells me the item is updating correctly. This looks like a trigger condition datatype mismatch rather than stale data.

For SharePoint boolean columns, the trigger often returns "0"/"1" instead of true/false. So, your condition: @equals(triggerBody()?['NotifyICAndICTEmail'], false) can behave unexpectedly.

Try this instead: @equals(triggerBody()?['NotifyICAndICTEmail'], 0) or: @equals(triggerBody()?['NotifyICAndICTEmail'], '0') depending on what you see in the raw trigger output.

Also, don’t trust the dynamic content preview but rather check the actual trigger JSON in the run history. SharePoint connectors are notorious for displaying boolean values inconsistently.

Please ✅ Does this answer your question if my post helped you solve your issue. This will help others find it more readily. It also closes the item.

If the content was useful in other ways, please consider answering Yes to Was this reply helpful? or give it a Like! 🩷

Was this reply helpful? Yes No