Hi Folks,

I’m running into what I think is unusual behavior with a sharepoint list.  Through the interface, if I select ~100 items, click edit, change a few fields and click save, it can take up to a few minutes before the data that I’ve changed shows up in rest calls filtering on those fields.  

I’ve tested this behavior in 3 ways:

Get Items action in a power automate flow using these fields in an odata filter

Filtering using CAML in a GetItems post call

Connection  & Query from Excel

In all cases the behavior is the same:  over the span of 4-5 minutes more and more of the items I modified become available in the results. The Modified timestamp on all of them however is the same (it’s the time I made the change).

For example: If I select then edit 160 rows and set the Action column (choice column) to “Add” and then immediately run a Get Items in power automate with this filter:   Action eq ‘Add’, on the first run, it’ll return 3 or 4 items, if I run it again it might return 10-15 items, If I run it 30 seconds later, it’ll return around 30-40 items and so on so forth until eventually a few minutes later it’ll return all the records that I had modified to Action = Add.   The modified timestamp on all the items however are the same. 

What’s also interesting is that on the list itself, it reflects the change immediately.  So what I see in the list is different than what’s being returned by filters against those fields.

Has anyone run into weird behavior like this?  It’s almost like there some sort of massive latency between the bulk edit action and the new data being available to filter against.

​Hi Folks, I’m running into what I think is unusual behavior with a sharepoint list.  Through the interface, if I select ~100 items, click edit, change a few fields and click save, it can take up to a few minutes before the data that I’ve changed shows up in rest calls filtering on those fields.  I’ve tested this behavior in 3 ways:Get Items action in a power automate flow using these fields in an odata filterFiltering using CAML in a GetItems post callConnection  & Query from Excel In all cases the behavior is the same:  over the span of 4-5 minutes more and more of the items I modified become available in the results. The Modified timestamp on all of them however is the same (it’s the time I made the change). For example: If I select then edit 160 rows and set the Action column (choice column) to “Add” and then immediately run a Get Items in power automate with this filter:   Action eq ‘Add’, on the first run, it’ll return 3 or 4 items, if I run it again it might return 10-15 items, If I run it 30 seconds later, it’ll return around 30-40 items and so on so forth until eventually a few minutes later it’ll return all the records that I had modified to Action = Add.   The modified timestamp on all the items however are the same.  What’s also interesting is that on the list itself, it reflects the change immediately.  So what I see in the list is different than what’s being returned by filters against those fields. Has anyone run into weird behavior like this?  It’s almost like there some sort of massive latency between the bulk edit action and the new data being available to filter against.     Read More

​