cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

Does "When a file is modified (Properties only)" include renaming file?

As described in the subject, I want to know does it include renaming a file? And if it is, how can I get the file's previous name? I created a flow with "When a file is modified (Properties only)" but when I changed a file name, the trigger isn't fired.

3 REPLIES 3
poweractivate
Most Valuable Professional
Most Valuable Professional

@treanityy 

 


@treanityy wrote:

does it include renaming a file?

 

Yes

 

Both the  When a file is modified (properties only) [OnUpdatedFilesV2] and When a file is modified [OnUpdatedFileV2] Triggers should work on both file editing and renaming - so in other words, for both triggers, editing the file contents, or even just renaming the file without editing the file contents, should fire both triggers in both cases.

 

I just tried it as well right now with the OneDrive for Business Connectors and Triggers, I was able to get both versions of the Triggers to fire when renaming the file, and that's even when the file contents were not edited

 

When editing a file contents, and also, when renaming a file without editing the file contents, I was able to get the triggers to fire in both cases.

 

There were some cases where I did not notice the triggers firing, but saw it appear in the Flow Run history some time later -  try seeing if waiting 5 to 15 minutes helps. It is possible to believe the trigger is not working because when you happened to test it, the one fired for editing the file but the one for renaming it fired later. This happened first to me and made it look like it didn't work for renaming the file, much like you write here. However, when I tested it multiple times instead of just a few times, I was able to get more misleading results that even both renaming and editing did not work. Instead,  the fact is, it was because the events came in a little bit later. Sometimes the events might come in later, see if waiting a bit helps. I did not notice that renaming necessarily came in later than editing - that only happened the first time I tested - after multiple tests, I was able to get them both to come in later, making it seem like it "didn't work at all". In fact, all events eventually came in within a few minutes, both for renaming, and for editing, and in all cases.

 

 

 

 

The When a file is modified (properties only) and When a file is modified should both work, and should both fire when the file is modified. Since renaming is a kind of modification, it should work, and I just tested it and it also works.

 

Renaming the file should fire both versions of the trigger When a file is modified (properties only) and When a file is modified 

Actually, "properties only" is not referring to renaming the file to cause the trigger to fire, that is referring to something else.

 

The words "properties only" in the When a file is modified (properties only) in the name of the trigger is not referring to properties that are the cause of the change, such as changing of the file name to trigger it  (despite this being in the title of the trigger in parentheses). Instead, it is referring to what the trigger will provide in the payload in When a file is modified (properties only) [OnUpdatedFilesV2] as opposed to When a file is modified [OnUpdatedFileV2]

 

In fact, both versions of the trigger should work for rename, because the word modified appears in both versions of the trigger title. The "properties only" actually means the following instead:

 

Specifically, it is that one trigger provides the File Content itself in the payload, whereas the other (the "properties only" one) does not, and provides, as it says in its name, "properties only". In any case, both of these triggers should fire when the file is renamed in OneDrive, even if the contents are not edited

 

You can check this difference on the  "When a file is modified" [OnUpdatedFileV2] - the one without the properties parenthetical:

 

When a file is modified

This operation triggers a flow when a file is modified in a folder. Files larger than 50 MB will be skipped and not returned by this trigger. [emphasis added]

Reason it might be skipping such big files more than 50MB is because, this trigger provides the actual File Content in the Trigger payload:

 

OnUpdatedFileV2.png

 

The (Properties Only) variant does not provide this.

Hence "Properties Only".

 

Other than this, both triggers should work even when renaming the file and not editing the contents.  

Note that the name given will be the name AFTER the rename - i.e. the new name and not BEFORE i.e. the previous name. Same with the file contents, for the version of the trigger that provides contents, it is the new contents which will be provided, not the previous contents.

 

I do recommend for you to use the "properties only" version of the trigger, if the file name is what is important and not the contents of the file.

 

 

As for the other question:

 


@treanityy wrote:

how can I get the file's previous name?


 

 

To my awareness, there is not a way to get the previous name. You might be able to instead ask people to use specific prefix or naming convention for specific files, and only change some part of the ending when making revision. In this case it might be possible to know which file it was which was changed without knowing the previous name. It might be helpful to know more about why the previous name specifically is important to be known.

 

In the case it is very important to know the previous filename. I am not aware of a Connector which does it out of the box right now, but it may be possible to retrieve this information. For the moment I won't answer in detail, but this might be possible starting point: Listing versions of a DriveItem or potentially Enumerate Activities - Note: I did not test if any of these will actually return a previous filename - it might, but I did not test that - it may be for you to find that out. 

 

In the case it is very important to get the previous filename and you would like some more detail and guidance on potential solutions for this, please share some more about your scenario just in case the previous filename is very important for your use case.

 

 

 

I've waited for it until now is almost 12 hours, but the flow is still not triggered after renaming a file. I'm sure that I've pointed the target folder the right way. In my case, I want to sync all my Onedrive files' activities with Google Drive, including update file content, renaming, etc... But it seems like I cannot sync the rename action. Is there any way to do it?

Hi @treanityy 

 

Did you got the answer for this?

 

I am also facing the same issue.

 

Thanks 

VK

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

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!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

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  

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

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.    

Updates to Transitions in the Power Platform Communities

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