SharePoint - When a file is created or modified (properties only) - One Flow trigger instance processing Multiple Files

[RobertRFreeman]

This action needs to be renamed (to be plural) since it can run on multiple files if they are uploaded simultaneously.  Alternatively, this should be redeveloped so it only runs on one file at a time (as currently named).  I was wondering why it automatically added a for each section whenever referencing the file properties, then I found out one trigger can run for multiple files.

New Name: When files are created or modified (properties only)

or

This action should only return one file.

Note: Currently a Trigger Condition that checks the first file would not catch the other files making Trigger Conditions worthless for this action. 

Example of a trigger condition that would only run on the 2nd version of the first file: @equals(triggerBody()?['Value'][0]['{VersionNumber}'], '2.0') but would either fail or pass for all the other files.

#bug

[Rhiassuring]

Well, a few things.

It SHOULD only return one file. 

Second, this isn't the place to report bugs. You'll want to submit that through the Power Automate feedback portal -- top right hand side in your maker portal.

But ... I have literally never seen what you're saying happen. If you uploaded multiple files, it should trigger once on each of those individual files. You're saying you've seen it trigger in a bulk upload to show all files in that bulk upload? Can you post a screenshot of your trigger output showing more than one file in it?

[grantjenkins]

This is caused by having Split On turned Off which means the trigger will run on batches of files. Some of the templates set this by default which is likely what happened here.

To fix the issue, click on the three dots ... on your Trigger and click on Settings, then set Split On to On and select the Array from the drop down. This will now set your trigger to work on one file at a time and won't give you the Apply to each.

[RobertRFreeman]

Thanks @grantjenkins , I didn't know about that setting.

This will likely cause problems for other developers who expect the trigger to function on one file, so renaming/fixing this is still necessary to prevent possible data loss or corruption (due to unclear naming).  Ideally there would be 2 differently named triggers one plural and one singular, even if the only change is this setting.

I'm confused why @Rhiassuring is recommending not posting bugs on a forum.  Yes, you should also report bugs to Microsoft via the help system, but you aren't helping anyone if you keep the info to yourself.  So, yes please post bugs here so we can all be aware of them and request fixes.

[Rhiassuring]

Sounds like it wasn't a bug at all, so, we're on the same page.

[RobertRFreeman]

@Rhiassuring, incorrect. You're 0 for 3 on this post.

[Rhiassuring]

If you read what @grantjenkins said, it is a toggle on an action that you inadvertently had switched; not your fault, it came from a template or something similar, pre-toggled. That's not a bug, it's a configuration. It's okay to not know. I didn't know, that's for sure! As I'd mentioned, I'd never seen it. @grantjenkins saved the day! Thanks, Grant!

[RobertRFreeman]

That's 0 for 4.  The bug is that it is off by default.  Yes, even without using a template.

Not sure why the devs would bury it in settings rather than putting it in parameters next to recurrence settings, where one would expect it.

It takes less than a minute to create a new Automate flow and verify this rather than continuing to make incorrect guesses.

[RobertRFreeman]

Split On functionality is extremely buggy and often unusable.

1
It skips versions.  Ex: If a file is uploaded and immediately modified, only the latest version will trigger the flow based upon the 5 minute interval (or whatever you set once MS fixes the bug in the interval interface).  If the flow is running while the version is updated you will get the prior version and the flow will never trigger on the latest version.  By default, flows should trigger on EVERY VERSION with the ability to use Trigger Conditions to stop the flows from running on specific edits.

2

Sometimes produces the following error and will need to rebuild the flow from scratch.  Due to can't remove the value or change it from the dropdown selections:
Unable to initialize operation details for operation - When_a_file_is_created_or_modified_(properties_only). Error details - Core.AssertionException: Invalid split on value '@triggerBody()?['body/value']', cannot find in outputs.

3

This error occurs if you disable Split On:
Unsupported split on expression '@triggerBody()?['body/value']'.

4

You cannot edit the Split On value in the new editor when the error in item 2 above occurs.

5
Where is the documentation for the Split On functionality and how to use the Tracking ID?