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
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?
I answer questions on the forum for 2-3 hours every Thursday!
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.
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.
Sounds like it wasn't a bug at all, so, we're on the same page.
I answer questions on the forum for 2-3 hours every Thursday!
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!
I answer questions on the forum for 2-3 hours every Thursday!
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.
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?
Dear Community Members, We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd. During this period, members will not be able to Kudo, Comment, or Reply to any posts. On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities. What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!
We are excited to announce the Summer of Solutions Challenge! This challenge is kicking off on Monday, June 17th and will run for (4) weeks. The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities. Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”) - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024 Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods. You must enter into each weekly Entry Period separately. How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different. Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers. At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing. Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner. A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random. Individuals will be contacted before the announcement with the opportunity to claim or deny the prize. Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners. Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event. ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE** Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersNumber SolutionsSuper UsersNumber Solutions Deenuji 9 @NathanAlvares24 17 @Anil_g 7 @ManishSolanki 13 @eetuRobo 5 @David_MA 10 @VishnuReddy1997 5 @SpongYe 9JhonatanOB19932 (tie) @Nived_Nambiar 8 @maltie 2 (tie) @PA-Noob 2 (tie) @LukeMcG 2 (tie) @tgut03 2 (tie) Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 2: Community MembersSolutionsSuper UsersSolutionsPower Automate @Deenuji 12@ManishSolanki 19 @Anil_g 10 @NathanAlvares24 17 @VishnuReddy1997 6 @Expiscornovus 10 @Tjan 5 @Nived_Nambiar 10 @eetuRobo 3 @SudeepGhatakNZ 8 Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji32ManishSolanki55VishnuReddy199724NathanAlvares2444Anil_g22SudeepGhatakNZ40eetuRobo18Nived_Nambiar28Tjan8David_MA22 Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 4:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji11FLMike31Sayan11ManishSolanki16VishnuReddy199710creativeopinion14Akshansh-Sharma3SudeepGhatakNZ7claudiovc2CFernandes5 misc2Nived_Nambiar5 Usernametwice232rzaneti5 eetuRobo2 Anil_g2 SharonS2
On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners. The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights. Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.
We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for. We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer. Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together. Here's to new beginnings and endless possibilities! If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport. To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages