Experts,
I need help in placing the 'Delay' to refresh my Power BI dataset after an hour. i.e., after the first refresh. In which step should I place it?
A | B | |
Step 1: Use 'When a new email arrives' action. | Step 1: Use 'When a new email arrives' action. | |
Step 2: Delay (for 1 hour) | OR | Step 2: Refresh a dataset |
Step 3: Refresh a dataset | Step 3: Delay (for 1 hour) |
Thanks for your help!
Solved! Go to Solution.
Hi @BBIUser
Here it is. I will check the value immediately and make sure whether I want to wait or not?
Step 1: 'When a new email arrives'
Step 2: Condition Value: Tigger Body Contains "Body text" (Example: Report Name has failed to refresh.)
Yes > Delay (for 1 hour)
Refresh a dataset
No > Exit
Thanks
If you liked my response, please consider giving it a thumbs up
Proud to be a Flownaut!
Learn more from my blogHi @BBIUser
Not sure what you trying to achieve here. Option B is my choice as it will refresh the dataset first and delay for an hour. What happens if no emails arrived for an hour or two. So there will be further delay after your one hour delay.
Thanks
If you liked my response, please consider giving it a thumbs up
Proud to be a Flownaut!
Learn more from my blogHi @BBIUser,
If you want to refresh the PowerBi dataset after 1 hour, the delay action should be in front of refresh action. So it should be Plan A.
Cause you said after the first refresh, I guess you want to refresh the PowerBi dataset twice and get a difference between the two refreshes.
The Plan should be:
A |
Step 1: Use 'When a new email arrives' action. |
Step 2: Refresh a dataset |
Step 3: Delay (for 1 hour) |
Step 4: Refresh a dataset |
Best Regards,
Community Support Team _ Lin Tu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
@v-litu-msft and @abm Thanks for your reply.
My apologizes, I should have mentioned this when I posted. I have schedule refreshes setup for all the datasets which will be my first refresh.
With this flow, I am avoiding to do manual dataset refreshes when there is failed or paused refreshes.
So basically, after the original schedule refresh, I am creating the flow which starts from
Step 1: Use 'When a new email arrives' action. |
There should be a delay for an hour after step 1 and then dataset should refresh.
I am guessing this should be my solution. Please correct me if I am wrong?
Step 1: Use 'When a new email arrives' action.
Step 2: Delay (for 1 hour)
Step 3: Refresh a dataset
Hi @BBIUser
After your first schedule refresh are you depending on email trigger to refresh the dataset via flow? Could you explain what this email is used for? Also overall process what you trying to achieve here.
Thanks
If you liked my response, please consider giving it a thumbs up
Proud to be a Flownaut!
Learn more from my blog@abm That is correct! I am depending on email trigger to refresh the dataset via flow.
Email will have the following:
To - My email address
From - Microsoft Power BI <no-reply-powerbi@microsoft.com>
Subject Filter - Refresh Failed
(or Paused - For this subject filter changes which is "Your scheduled refresh has been paused.")
Hi @BBIUser
Thanks for your quick reply. So this is used for whenever there is a failure happens you will receive an email, wait for an hour. I presume during this time this will be fixed in an hour and you want to refresh the dataset via flow? I still don't understand why wait for an hour? Also what will happen to your original scheduled trigger? Also if you receive more than one email then you have multiple triggers at the same time.
Thanks
If you liked my response, please consider giving it a thumbs up
Proud to be a Flownaut!
Learn more from my blogSo this is used for whenever there is a failure happens you will receive an email, wait for an hour. I presume during this time this will be fixed in an hour and you want to refresh the dataset via flow?
-- Correct! (and also for paused)
I still don't understand why wait for an hour?
-- Nothing specific. I can set it to even 5 mins. Assuming an hour to troubleshoot and fix it before this time.
Also what will happen to your original scheduled trigger?
-- Most of the schedules are daily or weekly. So it has to wait until next day or 1 week.
Also if you receive more than one email then you have multiple triggers at the same time.
-- I agree.
Assume, I have 10 different datasets. I am planning to create 10 flows.
I am new to Power Automate so not sure if this the correct approach to design for my use case. Any help is appreciated.
I am also trying this new design for the same use case:
Step 1: 'When a new email arrives'
Step 2: Delay (for 1 hour)
Step 3: Condition
Value: Tigger Body Contains "Body text" (Example: Report Name has failed to refresh.)
If Yes --
Refresh a dataset
If No --
Hi @BBIUser
Here it is. I will check the value immediately and make sure whether I want to wait or not?
Step 1: 'When a new email arrives'
Step 2: Condition Value: Tigger Body Contains "Body text" (Example: Report Name has failed to refresh.)
Yes > Delay (for 1 hour)
Refresh a dataset
No > Exit
Thanks
If you liked my response, please consider giving it a thumbs up
Proud to be a Flownaut!
Learn more from my blog@abm I did not know about the triggerBody(). Thanks for enlightening me on that.
Couple of questions:
1] No > Exit
-- Is 'Exit' an action that needs be applied? I thought 'If no' can be left empty which means Exit - am i correct?
2] Can I create a flow with 2 conditions? (Please see the screenshot) Will that work or is it a good design?
(This will have 9 flows for 10 datasets)
If this do not work, I will create new flow for the 2nd dataset (like as I said before that 10 datasets will have 10 flows)
I have 2 conditions in this flow because the Power BI Workspace has 2 different datasets in 1 Workspace.
So, both the conditions and other steps are same with just has different dataset name.
Here is my flow for Paused email trigger.
Hi @BBIUser
Couple of questions:
1] No > Exit
-- Is 'Exit' an action that needs be applied? I thought 'If no' can be left empty which means Exit - am i correct?
Yes can be empty or if you want to stop the flow then use terminate action.
2] Can I create a flow with 2 conditions? (Please see the screenshot) Will that work or is it a good design?
(This will have 9 flows for 10 datasets)
If this do not work, I will create new flow for the 2nd dataset (like as I said before that 10 datasets will have 10 flows)
I have 2 conditions in this flow because the Power BI Workspace has 2 different datasets in 1 Workspace.
Going with two conditions are ok but think about could you pass the dataset name as dynamic. Not sure that is supported in PowerBI action step. If it is that's your best option. Also splitting multiple flows are easy to manage and debug.
Thanks
If you liked my response, please consider giving it a thumbs up
Proud to be a Flownaut!
Learn more from my blogDear 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