You need to re-add the "When an existing item is modified" and "When an existing file is modified". It was replaced by "Created or Modified" and that is not sufficient. There are cases where certain logic is only executed on creation, and other logic only on modification. Now, don't get me wrong, created and/or modified running the same logic also has uses!
With only having the trigger "created or modified" and wanting only certain logic to run on a modification, I have to add logic to ignore creations. You're making more work for your users and taking away basic functionality.
on:
CDS new environment trigger event
on:
Organize PowerAutomate flows
Jinnie
on:
Create a repeat or loop feature in UI Flow.
on:
Folders for Flows
Hi everyone, thank you for the feedback, and apologies about the frustration you are feeling.
To clarify, we never had a "When an item/file is modified" trigger. It was called that, but the behavior was the same as what we have today. So we merely renamed it to reflect what it was doing, as it was causing a different kind of frustration.
The best way to identify item modified remains checking for the difference between created and modified timestamps to be "close enough". Most of the time these will be the same. However, things get out of sync when a large file is being uploaded, where the library item will get created, and then the file upload will complete and change the timestamp. Similarly, when creating a list item, first the item will be created, and then you will have modified events when each attachment completes uploading.
We will review how we can make this experience better, but it is a little challenging due to the reasons I tried to explain, so it will not be a quick fix that will be coming in a few weeks.