I have been working on a flow to send a task when any document has not been modified for one year. It is actually 11 months so we can provide evidence our documents are being reviewed. I have a flow that will reoccur daily and check the modified date but I only want to create a single task after 11 months (or 330 days). I have got it to work with less than or equal to but that will generate a task every day after that. I have tried a condition and filter array. The filter array does not actual filter my documents down. During my test it creates a task for every document and the condition comes back false. I have also calculated the days between dates and equal that to 30.
Here are the expressions I have used.
This example the document is 110 days old. Modified is equal to
addDays(utcNow(),-110,'yyyy-MM-dd')
Filter array 30 days before expiration
@equals(formatDateTime(utcNow(), 'yyyy-MM-dd'), addDays(item()?['OData__dlc_ExpireDate'], -30))
Count Days
eq(div(sub(ticks(formatDateTime(utcNow(),'yyyy-MM-dd')),ticks(outputs('Get_file_metadata')?['body/OData__dlc_ExpireDate'])),864000000000),30)
Any advice on getting any of these to work.
Solved! Go to Solution.
FYI I ended up adding a column to count the number of days from the last edit. Then I added the code to say if it was between the two values. Roundup was not working for the date to a whole number.
Age ge 110 and Age lt 111
I have a similar flow but it's scheduled - every morning it checks for files that are 30 days out from needing review (335 days so same as yours). It's worked really well so far - I initialize variables for the number of days so it's easier to change and then use that to configure a "Reset Date" variable:
The addDays formula is:
addDays(utcNow(), variables('varNumDays'), 'yyyy-MM-dd')
I call it the reset date because then I change the status from Approved to Draft along with sending a reminder email that the file needs reviewed. The only other modification I make is in my Get Items that follows:
So the Filter Query only gets items where their last update date is equal to the "reset date" and that's what gets reset/emailed about. Just another option to consider that I figured out and like!
@lsheltonSTO1 @ScottShearer
I took a bit of both of your advice. The formula was throwing an error but initializing the variables before hand removed the error. I could not get a successful test with Modified until I added the comparison to the query. I was able to create a single task for the correct file from the testing library. Thanks for both of your help.
leday
addDays(utcNow(), -335, 'yyyy-MM-dd')
geday
addDays(utcNow(), -336, 'yyyy-MM-dd')
Query
Modified ge '@{variables('geday')}' and Modified le '@{variables('leday')}'
A better way to approach this might be to use a recurrence trigger that fires daily and a get files properties only action that only retrieves items which meet your criteria. You'll use an OData filter (query filter) for this. Here is a good blog post on the topic.
Let me know if you need an example.
It ran but did not create a task. That is better than not filtering anything but there is a document that should match this query. Let me know if you have a better example.
Modified eq formatDateTime(addDays(utcNow(),-110,'yyyy-MM-dd'))
Try changing your filter to something like this:
Modified ge formatDateTime(addDays(utcNow(),-110,'yyyy-MM-dd')) and Modified lt formatDateTime(addDays(utcNow(),-109,'yyyy-MM-dd'))
The reason is that modified includes the time.
I am getting "The expression "Modified ge 2021-03-03T00:00:00.0000000 and Modified lt 2021-03-04T00:00:00.0000000" is not valid. Creating query failed."
FYI I ended up adding a column to count the number of days from the last edit. Then I added the code to say if it was between the two values. Roundup was not working for the date to a whole number.
Age ge 110 and Age lt 111
I have a similar flow but it's scheduled - every morning it checks for files that are 30 days out from needing review (335 days so same as yours). It's worked really well so far - I initialize variables for the number of days so it's easier to change and then use that to configure a "Reset Date" variable:
The addDays formula is:
addDays(utcNow(), variables('varNumDays'), 'yyyy-MM-dd')
I call it the reset date because then I change the status from Approved to Draft along with sending a reminder email that the file needs reviewed. The only other modification I make is in my Get Items that follows:
So the Filter Query only gets items where their last update date is equal to the "reset date" and that's what gets reset/emailed about. Just another option to consider that I figured out and like!
I'm glad that you got it working!
You said that you added a column. Please note that if it is a calculated column that your values will not be updated unless the document or document properties are edited.
I was wondering about the variables. Thank you!!!
@lsheltonSTO1 Do I need to format the Modified Date? I was going to use the expiration date but it is not on all documents (Some are too old). I can also create a new column if that might work better.
I didn't do anything to format my date columns - are you just using the out of the box Modified Date? I have two date columns I use in my total solution, Completion Date which is updated to the current date when the file is approved, and Review Date, which is a calculated column with the formula
=[Completion Date]+365
Then I use that Review Date column to detect 30 days out with my daily scheduled flow.
In your case, if you are wanting yearly reviews, we are still working out our go live and figuring out how to best determine when these documents we are moving into SharePoint need review without doing it manually. (I have a feeling that I'm going to be doing it manually) So, I don't have any tested advice there for you with that part of the process unfortunately. But I didn't have to format any of the dates beyond the basic date field (without time).
@lsheltonSTO1 @ScottShearer
I took a bit of both of your advice. The formula was throwing an error but initializing the variables before hand removed the error. I could not get a successful test with Modified until I added the comparison to the query. I was able to create a single task for the correct file from the testing library. Thanks for both of your help.
leday
addDays(utcNow(), -335, 'yyyy-MM-dd')
geday
addDays(utcNow(), -336, 'yyyy-MM-dd')
Query
Modified ge '@{variables('geday')}' and Modified le '@{variables('leday')}'
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