cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
RobinWhite5133
Frequent Visitor

Multi-level Filter Query in Power Automate

I have created a Risk Register using a SharePoint list and am trying to create a flow that will send a reminder email when a Risk is due for review.

 

The issue I am having is with the filter. I have a date when the last review was carried which I want to use, and 2 other columns which have numeric value based on the Residual Impact & Residual Probability of the Risk occurring creating a residual Risk Score.  When the Risk is due for review is dependent on 3 Elements 'The Last Review Date', 'The Residual Impact' and the 'Residual Probability'. For example, if the Review date was 90 days ago and the Residual Risk Score is Greater than or Equal to 4 and the Residual Probability is Greater than or Equal to 4 then an email reminder is sent to the Risk Owner.

 

Where it gets complicated (well for me anyway) is when the if the Review date was 180 days and the Risk has a Residual Risk score of between 8 & 15 I.E. 'Residual Impact' * 'Residual Probability' then I need the reminder email to be sent.

 

If anyone out there can help out it would be greatly appreciated.

 

This is my current flow:

                                                           RobinWhite5133_4-1687174350815.png

                                                          RobinWhite5133_1-1687174146229.png

                                                          RobinWhite5133_2-1687174209585.png

                                                            RobinWhite5133_3-1687174271293.png

 

1 ACCEPTED SOLUTION

Accepted Solutions

This is one way to do it.

 

{"id":"b11ed289-74e4-4388-9b8c-93a516e8d6cf","brandColor":"#8C3900","connectionReferences":{"shared_sharepointonline":{"connection":{"id":"/providers/Microsoft.PowerApps/apis/shared_sharepointonline/connections/shared-sharepointonl-b959cb53-5ecb-4b41-805f-06e7795a0bd2"}},"shared_commondataserviceforapps":{"connection":{"id":"/providers/Microsoft.PowerApps/apis/shared_commondataserviceforapps/connections/62947705b1a746319ca1e59aae985afc"}}},"connectorDisplayName":"Control","icon":"data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMzIiIGhlaWdodD0iMzIiIHZlcnNpb249IjEuMSIgdmlld0JveD0iMCAwIDMyIDMyIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPg0KIDxwYXRoIGQ9Im0wIDBoMzJ2MzJoLTMyeiIgZmlsbD0iIzhDMzkwMCIvPg0KIDxwYXRoIGQ9Im04IDEwaDE2djEyaC0xNnptMTUgMTF2LTEwaC0xNHYxMHptLTItOHY2aC0xMHYtNnptLTEgNXYtNGgtOHY0eiIgZmlsbD0iI2ZmZiIvPg0KPC9zdmc+DQo=","isTrigger":false,"operationName":"Scope_90,_180,_360_Filter","operationDefinition":{"type":"Scope","actions":{"Compose_Dummy_Response":{"type":"Compose","inputs":[{"Last Review Date":"2022-06-25","Residual Impact":4,"Residial Probability":1,"Risc Owner Email":"dummy@whatever.com"},{"Last Review Date":"2022-06-25","Residual Impact":3,"Residial Probability":2,"Risc Owner Email":"dummy2@whatever.com"},{"Last Review Date":"2022-06-25","Residual Impact":4,"Residial Probability":3,"Risc Owner Email":"dummy3@whatever.com"},{"Last Review Date":"2022-06-25","Residual Impact":3,"Residial Probability":5,"Risc Owner Email":"dummy4@whatever.com"},{"Last Review Date":"2022-06-25","Residual Impact":5,"Residial Probability":5,"Risc Owner Email":"dummy5@whatever.com"},{"Last Review Date":"2023-03-22","Residual Impact":4,"Residial Probability":4,"Risc Owner Email":"dummy6@whatever.com"},{"Last Review Date":"2022-12-22","Residual Impact":4,"Residial Probability":3,"Risc Owner Email":"dummy7@whatever.com"}],"runAfter":{}},"Select_Response":{"type":"Select","inputs":{"from":"@outputs('Compose_Dummy_Response')","select":{"Days":"@int(first(split(dateDifference(item()['Last Review Date'], take(utcNow(),10)), '.')))","Score":"@mul(item()['Residual Impact'],item()['Residial Probability'])","Risc Owner Email":"@item()['Risc Owner Email']"}},"runAfter":{"Compose_Dummy_Response":["Succeeded"]}},"Filter_Response":{"type":"Query","inputs":{"from":"@body('Select_Response')","where":"@equals(or(and(equals(item()['Days'], 180), and(greaterOrEquals(item()['Score'], 8), lessOrEquals(item()['Score'], 15))), or(and(equals(item()['Days'], 90), greaterOrEquals(item()['Score'], 16)), and(equals(item()['Days'], 360), lessOrEquals(item()['Score'], 7)))), true)"},"runAfter":{"Select_Response":["Succeeded"]}},"Apply_to_each":{"type":"Foreach","foreach":"@body('Filter_Response')","actions":{"Compose_Send_email":{"type":"Compose","inputs":"No send an email to @{items('Apply_to_each')['Risc Owner Email']}","runAfter":{}}},"runAfter":{"Filter_Response":["Succeeded"]},"runtimeConfiguration":{"concurrency":{"repetitions":50}}}},"runAfter":{}}}

 

You won't need variables or branches and the flow will run very quickly. Just copy that source in you clipboard and add it to a dummy flow to see what is going on. If you have problems implementing it in your flow, just give me an update, but I will need some details (structure) of the fields you get from the sharepoint list.

View solution in original post

6 REPLIES 6

Hello @RobinWhite5133 ,

 

you should filter the data before you use the "apply to each" action. In that case you can loop through all the remaining items and do not have to check the condition inside the loop. Best way is during the "get items" action. Another way would be "filter array". Of course you need to implement the logic too but it would save time during the loop.

 

Can you please explain again all the conditions. In your sample you talk about 90 days in another sample you talk about 180 days and in the flow I only see the 180 days condition.

@RobinWhite5133 I am also confused a little between the explanation and the screenshot, but if I understood  the question correctly, you can use this expression in your condition to check the Risk, just replace the variables inside the mul function.

 

if(or(greaterOrEquals(mul('Residual Impact','Residual Probability'),8),lessOrEquals(mul('Residual Impact','Residual Probability'),15)),true, false)

 

Matthy, I only copied the 180 Condition as the flow has parallel branches and was too big. Below are the 90 day & 360 day conditions I have put in:

 

90 Days

 

                          RobinWhite5133_0-1687251438115.png

                       RobinWhite5133_1-1687251478808.png

360 Days

                                     RobinWhite5133_2-1687251591543.png

 

                                 RobinWhite5133_3-1687251628479.png

 

In essence what I am trying to do is send an email reminder if the follwing conditions are met:

 

if the following is true:

  • Residual Risk Score (Residual Impact*Residial Probability) is equal to or greater then 16, and days since last review date is 90 days.
  • Residual Risk Score (Residual Impact*Residial Probability) is between 8 & 15, and days since last review date is 180 days.
  • Residual Risk Score (Residual Impact*Residial Probability) is equal or less than 7, and days since last review date is 360 days.

The above is based on a 5x5 matrix as shown below:

RobinWhite5133_4-1687252440176.png

 

Hope that all makes sense.. I just can't get my head around it...

 

KR

Robin

 

This is one way to do it.

 

{"id":"b11ed289-74e4-4388-9b8c-93a516e8d6cf","brandColor":"#8C3900","connectionReferences":{"shared_sharepointonline":{"connection":{"id":"/providers/Microsoft.PowerApps/apis/shared_sharepointonline/connections/shared-sharepointonl-b959cb53-5ecb-4b41-805f-06e7795a0bd2"}},"shared_commondataserviceforapps":{"connection":{"id":"/providers/Microsoft.PowerApps/apis/shared_commondataserviceforapps/connections/62947705b1a746319ca1e59aae985afc"}}},"connectorDisplayName":"Control","icon":"data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMzIiIGhlaWdodD0iMzIiIHZlcnNpb249IjEuMSIgdmlld0JveD0iMCAwIDMyIDMyIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPg0KIDxwYXRoIGQ9Im0wIDBoMzJ2MzJoLTMyeiIgZmlsbD0iIzhDMzkwMCIvPg0KIDxwYXRoIGQ9Im04IDEwaDE2djEyaC0xNnptMTUgMTF2LTEwaC0xNHYxMHptLTItOHY2aC0xMHYtNnptLTEgNXYtNGgtOHY0eiIgZmlsbD0iI2ZmZiIvPg0KPC9zdmc+DQo=","isTrigger":false,"operationName":"Scope_90,_180,_360_Filter","operationDefinition":{"type":"Scope","actions":{"Compose_Dummy_Response":{"type":"Compose","inputs":[{"Last Review Date":"2022-06-25","Residual Impact":4,"Residial Probability":1,"Risc Owner Email":"dummy@whatever.com"},{"Last Review Date":"2022-06-25","Residual Impact":3,"Residial Probability":2,"Risc Owner Email":"dummy2@whatever.com"},{"Last Review Date":"2022-06-25","Residual Impact":4,"Residial Probability":3,"Risc Owner Email":"dummy3@whatever.com"},{"Last Review Date":"2022-06-25","Residual Impact":3,"Residial Probability":5,"Risc Owner Email":"dummy4@whatever.com"},{"Last Review Date":"2022-06-25","Residual Impact":5,"Residial Probability":5,"Risc Owner Email":"dummy5@whatever.com"},{"Last Review Date":"2023-03-22","Residual Impact":4,"Residial Probability":4,"Risc Owner Email":"dummy6@whatever.com"},{"Last Review Date":"2022-12-22","Residual Impact":4,"Residial Probability":3,"Risc Owner Email":"dummy7@whatever.com"}],"runAfter":{}},"Select_Response":{"type":"Select","inputs":{"from":"@outputs('Compose_Dummy_Response')","select":{"Days":"@int(first(split(dateDifference(item()['Last Review Date'], take(utcNow(),10)), '.')))","Score":"@mul(item()['Residual Impact'],item()['Residial Probability'])","Risc Owner Email":"@item()['Risc Owner Email']"}},"runAfter":{"Compose_Dummy_Response":["Succeeded"]}},"Filter_Response":{"type":"Query","inputs":{"from":"@body('Select_Response')","where":"@equals(or(and(equals(item()['Days'], 180), and(greaterOrEquals(item()['Score'], 8), lessOrEquals(item()['Score'], 15))), or(and(equals(item()['Days'], 90), greaterOrEquals(item()['Score'], 16)), and(equals(item()['Days'], 360), lessOrEquals(item()['Score'], 7)))), true)"},"runAfter":{"Select_Response":["Succeeded"]}},"Apply_to_each":{"type":"Foreach","foreach":"@body('Filter_Response')","actions":{"Compose_Send_email":{"type":"Compose","inputs":"No send an email to @{items('Apply_to_each')['Risc Owner Email']}","runAfter":{}}},"runAfter":{"Filter_Response":["Succeeded"]},"runtimeConfiguration":{"concurrency":{"repetitions":50}}}},"runAfter":{}}}

 

You won't need variables or branches and the flow will run very quickly. Just copy that source in you clipboard and add it to a dummy flow to see what is going on. If you have problems implementing it in your flow, just give me an update, but I will need some details (structure) of the fields you get from the sharepoint list.

Hi Matthy

 

Sorry but I'm a little confused. Where in the flow do I put the code above? Is it as an expression or just into the Filter Query in the Get Items action? KR Robin

You can't use this source in your flow. As mentioned I don't have the information to send you an update. This is just a sample how to do it. Put it in a dummy flow and see how it works. After that you can update your flow. If you need further assist, you will have to give more details about the fieldnames. But please have a look at the sample first.

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

Users online (944)