I'm trying to have a flow run at SUNRISE each day for certain geographic locations. Has anyone done this?
Solved! Go to Solution.
Hi @cwomack,
Well, that worked! Kind of nifty actually 🙂
Here's the Flow I tested with, with some explanation below:
So... every Flow must have a trigger of some sort, something that sets it off. Unfortunately, the two triggers available with the MSN Weather connector are only related to the current weather (i.e. When the current conditions change, and When the current weather measure changes). However, the sunrise and sunset times (and lots of other things) are available in the weather forecast coming from this connector. But that's an Action: Get forecast for today. So that can only be used within a Flow that's already been triggered. So for a trigger, I chose Recurrence - it sounds like you've already found that trigger, but what I did here was set it to trigger daily at some hour before sunrise, e.g. 4am. [Actually, my Flow is testing for sunset, so that I could test it today without waiting for tomorrow's sunrise, so I set it to trigger at 4pm 🙂 ]
Next is the MSN Weather action Get forecast for today. Here, you specify the location, and the unit of measure you want to use (i.e. F vs C temp). You can just type in a city and country, or enter a longitude and latitude, or various other things (there's a tip in the box about that). I happen to be in Costa Rica right now, so that's what I entered 🙂
In the next step, I found I needed to do a bit of trickery with the value that came back from MSN Weather for the sun[set] time. It came back in a format like 2018-04-16T23:46:50+00:00, but the following step needed it to be in standard UTC format like 2018-04-16T23:46:50Z. So the Compose action uses an expression to modify the text:
substring(body('Get_forecast_for_today')?['responses']?['almanac']?['sunset'],0,19)
[I created the expression by using the Expression Builder, but the above is what comes out of it.] Basically, I'm getting the first 19 characters of the sunset time, i.e. removing the +00:00 from the end.
The next action is Delay Until, which pauses the Flow until a certain time. Here, the time is the output of the Compose step, with a Z added to the end to meet the format requirement. I have to say that datetime manipulation is one of the trickier things about Flow 😕 Something to be aware of is that all datetime outputs of a Flow action are in UTC time. So while the sunset value of the MSN Weather action was 23:46, that equated to the actual sunset time here in Costa Rica of 17:46.
And then after that you can do whatever actions you wanted to do. I just sent myself a mobile notification, which came in at 5:46p as the sun was setting over the mountains.
I hope this helps you! I found it to be a very interesting scenario, so I think I'll write a blog post about it for the Flow Community Blog. The post will have more screenshots and details, so if something above wasn't quite clear, I hope the post will help further 🙂
Sandy
Proud to be a Flownaut!
Hi @ cwomack,
Could you please explain more about the "SUNRISE each day" that you mentioned?
Do you mean a specific time such as "6 am" every day at your geographic locations?
Or do you mean the time when the sun start to shine at your geographic locations?
If you want the flow to run at a specific time such as "6 am" every day at your geographic locations, you could count want is the utc time at your geographic locations time "6 am",and if the utc time is "5 am" at your geographic locations time "6 am", you could add a flow with trigger "recurrence", and configue the "recurrence" to run at "5 am" every day as below:
If you want the flow to run when the sun start to shine at your geographic locations, it is not supported in microsoft flow currently,I afraid that there is no way to achieve your needs in Microsoft Flow currently.
If you would like this feature to be added in Microsoft Flow, please submit an idea to Flow Ideas Forum:
https://powerusers.microsoft.com/t5/Flow-Ideas/idb-p/FlowIdeas
Regards,
Alice Zhang
Setting a trigger at a certain time each day is easy enough. I want a flow triggered based on the SUNRISE time each day, which will be a different time each day.
Example sunrise times for Dallas, Texas: https://www.timeanddate.com/sun/usa/dallas
Hi @cwomack,
This is a pretty interesting use case!
I haven't tried it myself, but can you make use of the MSN Weather connector? The triggers are only on when some aspect of the current weather changes, but there's an action to get today's forecast, which includes sunrise time. Maybe you could trigger the Flow at a pre-sunrise time each day (e.g. 3am or something), get today's sunrise time for the location, and then Delay Until that time. And then do whatever you wanted to do at that time.
Just sort of thinking aloud, but I think that could work...
Proud to be a Flownaut!
SandyU, that's the only connector with a sunrise definition, but I'm not sure how to use that as a trigger. I'm fairly new to Flows. I just need a simple trigger when the sunrises each day to send an email.
How would I "get" the sunrise time?
Thanks!
Here's a thought...
A quick search for how to calculate sunrise took me here: https://en.wikipedia.org/wiki/Sunrise_equation
Why not use Excel to calculate the exact time for sunrise on a given day using the equation shown in the post I referenced above.
Using a Recurrence trigger that runs every day, add a row to the Excel table with the current date.
Then retrieve the calculated times for each location specified in the Excel table.
Then use a delay action and send out the email at the specified time.
I haven't tested this yet (and the calculation is a is not trivial) but I believe that it should work.
Hi @cwomack,
I'm testing this idea out on a sunset "trigger" this evening, and I'll get back to you 🙂
Sandy
Proud to be a Flownaut!
Hi @cwomack,
Well, that worked! Kind of nifty actually 🙂
Here's the Flow I tested with, with some explanation below:
So... every Flow must have a trigger of some sort, something that sets it off. Unfortunately, the two triggers available with the MSN Weather connector are only related to the current weather (i.e. When the current conditions change, and When the current weather measure changes). However, the sunrise and sunset times (and lots of other things) are available in the weather forecast coming from this connector. But that's an Action: Get forecast for today. So that can only be used within a Flow that's already been triggered. So for a trigger, I chose Recurrence - it sounds like you've already found that trigger, but what I did here was set it to trigger daily at some hour before sunrise, e.g. 4am. [Actually, my Flow is testing for sunset, so that I could test it today without waiting for tomorrow's sunrise, so I set it to trigger at 4pm 🙂 ]
Next is the MSN Weather action Get forecast for today. Here, you specify the location, and the unit of measure you want to use (i.e. F vs C temp). You can just type in a city and country, or enter a longitude and latitude, or various other things (there's a tip in the box about that). I happen to be in Costa Rica right now, so that's what I entered 🙂
In the next step, I found I needed to do a bit of trickery with the value that came back from MSN Weather for the sun[set] time. It came back in a format like 2018-04-16T23:46:50+00:00, but the following step needed it to be in standard UTC format like 2018-04-16T23:46:50Z. So the Compose action uses an expression to modify the text:
substring(body('Get_forecast_for_today')?['responses']?['almanac']?['sunset'],0,19)
[I created the expression by using the Expression Builder, but the above is what comes out of it.] Basically, I'm getting the first 19 characters of the sunset time, i.e. removing the +00:00 from the end.
The next action is Delay Until, which pauses the Flow until a certain time. Here, the time is the output of the Compose step, with a Z added to the end to meet the format requirement. I have to say that datetime manipulation is one of the trickier things about Flow 😕 Something to be aware of is that all datetime outputs of a Flow action are in UTC time. So while the sunset value of the MSN Weather action was 23:46, that equated to the actual sunset time here in Costa Rica of 17:46.
And then after that you can do whatever actions you wanted to do. I just sent myself a mobile notification, which came in at 5:46p as the sun was setting over the mountains.
I hope this helps you! I found it to be a very interesting scenario, so I think I'll write a blog post about it for the Flow Community Blog. The post will have more screenshots and details, so if something above wasn't quite clear, I hope the post will help further 🙂
Sandy
Proud to be a Flownaut!
Excellent Sandy, I've marked this as the solution!
Great... happy to help!
Here's the blog post I wrote about it - I hope you don't mind my using your question that way 🙂
Sandy
Proud to be a Flownaut!
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