cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
daxjkent
Advocate III
Advocate III

Run a Child Flow Action now has required Fields. Date, Full Address, Country, City, State, Street, Postal, Latitude, Longitude

Simplified example.   New Cloud flow with Manual Trigger and no inputs.

daxjkent_0-1648151153587.png

2nd Manually triggered flow that calls the first Flow in a "Run a Child Flow" action.

daxjkent_1-1648151196554.png

9 required inputs that were not referenced in the original a trigger.  When did this requirement start for Child Flows and is it going to wreak havoc with all of our existing Child flows.

 

18 REPLIES 18
manuelstgomes
Community Champion
Community Champion

Hi @daxjkent 

 

That doesn't make sense indeed. I smell a bug or something that went wrong in a deployment from Microsoft's site.

 

I tried to replicate the issue on two tenants, and all is ok, so it's probably something that we need to wait for Microsoft to solve. I know it sucks, but the alternative is to contact the support and check if they can help.

 

Cheers
Manuel

------------------------------------------------------------------
If I have answered your question, please mark it as "Accept as Solution." It will help other members find the solution faster. If you like my response, please give it a Thumbs Up. ?
Otherwise, reply to it, and the community will do its best to help you.

DKassian
Advocate IV
Advocate IV

I am getting this same behavior in multiple environments, along with a bunch of other flow bugs (actions not loading, formula editor not loading, error accessing local storage notification). 

 

I suspect once again Microsoft has pushed updates without understanding the implications or properly testing. I have not seen any impact to existing child flows, it is only impacting new flows - hopefully it stays that way.

Anonymous
Not applicable

Thanks for raising this. I thought it was only me that encounter this issue. 

 

In my flow, the location parameters are not required but an error still pops up saying that they are required. 

keithmcclungeip
Advocate I
Advocate I

I have the same issue. I've found that by using the trigger "PowerApps V2" instead of "Manually trigger a flow" you can run the flow as a child without all the other fields being required. May not help you if you specifically need it to be manually triggered however.

daxjkent
Advocate III
Advocate III

Thanks for the suggestion.  This is some super heavy modification in some flows when the variable from the trigger is used thru the entire flow.  

 

Ideally Power Automate could just get their quality control working better and not inflict these random issues that cause massive mayhem and disruption in production environments.

daxjkent
Advocate III
Advocate III

I've had to resort to this in a pile of flows just to get them running again.

daxjkent_0-1648835821087.png

 

joelzehring
Advocate IV
Advocate IV

We're also experiencing failed flows related to this issue.

Anonymous
Not applicable

Microsoft support just came back to me and the solution they proposed is working now. What they proposed is that you have to remove the trigger of the childflow and add it back again. 

 

Yes, I agree it's tedious because I am doing the same thing as well. 

 

Please mark this as a solution if it works for you as well. Thanks! 

daxjkent
Advocate III
Advocate III

Yes we were informed of this "solution" as well, but we will not be doing this due to the size of some of the flows infected. 

Please keep in mind, in order to remove a trigger action, you must remove all references to that trigger action thru the entire flow.  In larger flows this is essentially a complete dismantle and rebuild of what was previously a properly working flow.  The old adage of "if it aint' broke, don't fix it" comes to mind.  It was never the child flow that was the issue, it was the parent flow calling it.  The fix needs to happen at the parent level in order for it to be considered resolved in my eyes.

daxjkent
Advocate III
Advocate III

I did just test this proposed fix on a smaller child flow, what is failed to be mentioned is that this proposal also requires you to modify ALL of the parent flows referencing the child flow as well since the "Run a child Flow" action is now passing variables to a child flow that are no longer being requested when you replace the trigger action in the child flow.

Anonymous
Not applicable

Yes, I understand the situation and I was frustrated to know that this is the solution proposed by them.

 

I definitely agree with you because my child flow is very large as well. I have to be very careful to add the dynamic content back to my flow again. Luckily my parent flow does not required any input from the child flow, which saves me the trouble and time to add the dynamic content to each of my parent flow. 

 

Also, I am not sure what kind of help can they provide besides asking for more screenshots of my flow and try this tedious step. If anyone comes up with anything, please share. 

FinderFees
Advocate II
Advocate II

Sorry to revive an older post, but since this thread is one of the first results when doing a Google search on this issue, I just wanted to add a bit here that could be helpful for some or at the very least potentially provide some information/context that I discovered. (Really just trying to justify the amount of time I've spent on this...)

I also wanted to note that we recently saw this after enabling "Experimental Features" in this environment (luckily it's just dev). So there is a potential that this is the result of one of those features, and is ultimately self-inflicted pain. If that's the case, then there is the potential for it to be re-introduced upon the official feature release. Or it's entirely unrelated and we just got unlucky. 😉

As other posts have said, this is not so much an issue with the "Run a Child Flow" action as it seems to be with that child flow's "Manually trigger a flow" trigger.

Using the "Peek Code" option on the trigger, I was able to see that indeed certain fields, such as 'key-button-date' and 'location' were being required in the JSON.

 

 

FinderFees_0-1668727858419.png


The proper working functionality is that if you reference the trigger's various "extra" options such as "Date", "Full address", "Latitude", etc (available by default in the "Dynamic content" popup) within a flow action, these properties get automatically added to the trigger and are required. You can't see them IN the trigger without peeking the code, but they are there.

 

Now the reason I'm sure we are all here, is that we didn't in fact reference these items within the flow. So the question then becomes how did they get there and why can't they be removed?

 

From my testing, the best initial description of the issue I can come up with is that those properties have somehow become disassociated with whatever process is used to add and remove them dynamically from the trigger.

 

Interestingly enough, I was able to go in and create a new "Compose" action where I intentionally added a reference to the trigger's date (aka 'key-button-date'), saved, and then removed the reference. When I peeked the code of the trigger again, the 'key-button-date' property also was removed! I was excited and thought I had stumbled upon a true fix that user's could implement, until I subsequently tested with various location-based fields and had no such success. I tried many combinations of trying to remove whole large objects such as the generic 'address' to small independent fields, such as 'Postal code', and could not get the "fix" to happen again. 😞

 

I also went into another environment, created a new flow, added all the fields to a Compose action (and thus the trigger) and reviewed the JSON and could not find anything obvious like a property or order change. They also all removed just fine as expected. So I'm really not sure why Power Automate refuses to clean up it's own trigger code in this one specific case.

 

Anyway... the "true" fix that I did is not the Microsoft recommended fix, and I can't really say if it's more or less risky or annoying than deleting and re-adding a trigger, but for me it made more sense.

 

I am using Solutions in my environment and I "simply" (relative to your personal experience lol) exported the unmanaged Solution and updated the flow's JSON to remove the offending schema. If you are going to attempt this, you'll need a text editor like notepad++ and for sure a test environment to ensure everything comes back in properly.

 

Also I would recommend keeping a copy of your unaltered exported solution somewhere, just in case something doesn't seem to be working correctly afterword.

 

Unzip the exported .zip file, go into the Workflows folder and open the flow JSON in your editor of choice.

 

The first step - if you aren't 100% sure that you absolutely were not referencing this item in an action - is to do a "Find" for one of the offending items. For instance, if I was referencing the "Latitude" property in my flow, I would see the following "triggerBody()" statement in an action property:

 

FinderFees_2-1668728889398.png

 

If you find something like this. STOP. Go back into your flow in Power Automate and delete that reference first and see if it clears up your issue.

 

If you are like me, where the only two finds for 'location' were within the trigger itself, then you can move on to editing the JSON.

 

You'll be looking for the below data (displayed in VSC for readability) under the "triggers" property. (Truly, your 'location' object will likely be much longer than this, I just recreated a simple example for this screenshot).

 

FinderFees_1-1668728533888.png

 

You then want to delete everything in the yellow boxes (the entire location object), being careful to ensure you also remove the preceding commas and don't accidently remove an extra brace/bracket. Also don't forget to remove the reference to the location property in the "required" array - also highlighted above.

 

After doing this, you can save and close that file. Then open the "solution.xml" file and update the version to a newer one:

 

FinderFees_3-1668729187344.png

 

Then go in and re-zip your solution. Your folder structure should look like MySolution_VersionNumber.zip -> "Workflows" folder, solution.xml + other files. Don't zip at the top level and include an additional parent folder or it won't import properly.

Once that's all done, go ahead and attempt to re-import your solution. If successful, when you edit your flow and peek the trigger code, you'll see the offending required items are gone. Additionally, when you go into your "Parent" flow and view the "Run a Child Flow" action, the extra fields will be gone and will allow you to save without unwanted "required" fields.

 

Hope this helps someone. 🙂

Thank you so much for sharing this information! It fixed the issue perfectly. I combined the knowledge of where/how to remove with the Postman update hack (from here) to update the flow without exporting/modifying/importing. Awesome!

Yrisson55
New Member

Hello Team, I have another workaround that may be simpler and I hope it can help someone.

 

Just delete the trigger and create it again with the same input fields. Then run a new parent flow test (do not resubmit a previous test, because this makes the issue again).

 

Please let me know if you have any questions!.

autopower
Helper I
Helper I

I just got hit by the very same bug now. I guess I will just need to recreate the trigger then.

anthonys123
Post Patron
Post Patron

I was about to create a new post about this exact same issue I've encountered. I ran the child flow as a test and the main flow added these required fields. I do not have experimental features enabled in this environment.   

 

So, what was working just fine is now going to take me how long to fix on my own? There seems to be a few different options to resolve this issue so I'll need to take the rest of my day to see which one works without breaking everything. Just another day behind schedule.... Thanks Microsoft!

LenC
Helper V
Helper V

For those who may come across this thread and wonder if the issue is still there....

This just happened to me as well.

 

I do not know if I briefly used one of those weird auto-parameters, causing the issue.

I do know I was using make.powerautomate.com with the "New" interface.  I won't be using either of those again...

 

Worked... Thanks!

Helpful resources

Announcements

Summer of Solutions | Week 3 Results | Win free tickets to the Power Platform Conference

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  

Copilot Cookbook Challenge | WINNERS ANNOUNCED | Win Tickets to the Power Platform Conference

We are excited to announce the "The Copilot Cookbook Community Challenge random winners have been selected for the Challenge.  Thank you to everyone who participated in this challenge.    Copilot Cookbook Gallery:Power Apps Cookbook Gallery: 1. @swaminawale  1. @renatoromao     2.  @SpongYe  2.   @nickpotts10  *Please note if for any reason a winner declines, we will have another random drawing.   Check out all of the Cookbook Submissions: 1. Copilot Studio Cookbook Gallery: https://aka.ms/CS_Copilot_Cookbook_Challenge 2. Power Apps Copilot Cookbook Gallery: https://aka.ms/PA_Copilot_Cookbook_Challenge   There will be 5 chances to qualify for the final drawing: Early Bird Entries: March 1 - June 2Week 1: June 3 - June 9Week 2: June 10 - June 16Week 3: June 17 - June 23Week 4: June 24 - June 30WINNERS ANNOUNCED - JULY 8th     At the end of each week, we will draw 5 random names from every user who has posted a qualifying Copilot Studio template, sample or demo in the Copilot Studio Cookbook or a qualifying Power Apps Copilot sample or demo in the Power Apps Copilot Cookbook. Users who are not drawn in a given week will be added to the pool for the next week. Users can qualify more than once, but no more than once per week. Four winners will be drawn at random from the total qualifying entrants. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once. If they are drawn multiple times, another user will be drawn at random. Prizes:  One Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value, does not include travel, lodging, or any other expenses) Winners are also eligible to do a 10-minute presentation of their demo or solution in a community solutions showcase at the event. To qualify for the drawing, templates, samples or demos must be related to Copilot Studio or a Copilot feature of Power Apps, Power Automate, or Power Pages, and must demonstrate or solve a complete unique and useful business or technical problem. Power Automate and Power Pagers posts should be added to the Power Apps Cookbook. Final determination of qualifying entries is at the sole discretion of Microsoft. Weekly updates and the Final random winners will be posted in the News & Announcements section in the communities on July 29th, 2024. Did you submit entries early?  Early Bird Entries March 1 - June 2:  If you posted something in the "early bird" time frame complete this form: https://aka.ms/Copilot_Challenge_EarlyBirds if you would like to be entered in the challenge. Early Bird Submissions: @renato 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. Copilot Cookbook Gallery:Power Apps Cookbook Gallery:1.  @Mathieu_Paris 1.   @SpongYe 2.  n/a2.   @Deenuji 3.  n/a3.   @Nived_Nambiar  4.  n/a4.   @ManishSolanki 5.  n/a5.    n/a   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. Copilot Cookbook Gallery:Power Apps Cookbook Gallery:1. Kasun_Pathirana1. ManishSolanki2. cloudatica2. madlad3. n/a3. SpongYe4. n/a4. n/a5. n/a5. n/a     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. Copilot Cookbook Gallery:Power Apps Cookbook Gallery:1. Parul_Yadav_Neo1. n/a2. SpongYe2. n/a3. n/a3. n/a4. n/a4. n/a5. n/a5. n/a   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.   Copilot Cookbook Gallery:Power Apps Cookbook Gallery:1. @nickpotts10  1. @ShrushtiShah  2. @Suniti_0020 2. @swaminawale 3. n/a3. @farukhis786 4. n/a4. @ManishSolanki  5. n/a5.  n/a

Important Update for Community Platform Access | READ ONLY July 16-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!

Tuesday Tip | How to Become a Community Blog Author

It's time for another TUESDAY TIPS, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community.   This Week's Topic: How to Become a Community Blog Author We want YOU to be part of the community blog! Sharing your knowledge of Power Platform is an essential part of our community! Here's why:   It helps create a vibrant and dynamic community of makers who can learn from each other’s experiences and insights.It provides a platform for collaboration and innovation, where members can share their ideas and work together to develop new solutions.It helps promote Power Platform by showcasing its capabilities and real-world applications.It helps build trust and credibility in the community because you are providing valuable information and resources your fellow community members can use to improve their skills and knowledge. By sharing your knowledge of Power Platform in the community blog, you help us create a more engaged and informed community, better equipped to tackle complex challenges. To get started with blogging across the Power Platform communities, please visit the following links:   Power Apps: https://powerusers.microsoft.com/t5/Power-Apps-Community-Blog/bg-p/PowerAppsBlog Power Automate: https://powerusers.microsoft.com/t5/Power-Automate-Community-Blog/bg-p/MPABlog Copilot Studios: https://powerusers.microsoft.com/t5/Power-Virtual-Agents-Community/bg-p/PVACommunityBlogPower Pages: https://powerusers.microsoft.com/t5/Power-Pages-Community-Blog/bg-p/mpp_blog   When you follow the link, look for a button like the one below on the right rail of your community blog, and let us know you're interested. We can't wait to connect with you and help you get started. Thanks for being part of our incredible community--and thanks for becoming part of the community blog!  

June 2024 Community Newsletter

It's time for the June Community Newsletter, where we highlight the latest news, product releases, upcoming events, and the amazing work of our outstanding Community members.   If you're new to the Community, please make sure to follow the latest News & Announcements and check out the Community on LinkedIn as well! It's the best way to stay up-to-date with all the news from across Microsoft Power Platform and beyond.    COMMUNITY HIGHLIGHTS   Check out the most active community members of the last month! These hardworking members are posting regularly, answering questions, kudos, and providing top solutions in their communities. We are so thankful for each of you--keep up the great work! If you hope to see your name here next month, follow these awesome community members to see what they do!   Power AppsPower AutomateCopilot StudioPower PagesWarrenBelzcreativeopinionExpiscornovus Fubar AmikNived_NambiarPstork1OliverRodriguesmmbr1606ManishSolankifernandosilvaragavanrajanBCBuizerExpiscornovusrenatoromaoLucas001timlAlexEncodianViswavEmadBeshaiDBO_DVDeenujiUmiantaChrist0fGochixVishnuReddy1997citron-trucmandelaVishalJhaverieetuRoboJohanTprathyooanandm08VictorIvanidzenicoxrfm1964shashankbhidepaulbeck1 rpaa   LATEST NEWS Summer of Solutions 2024 The Summer of Solutions challenge kicked off this month - an amazing Microsoft Community initiative to win free tickets to the Power Platform Community Conferencethis September in Las Vegas. The challenge is NOW OPEN to all #PowerPlatform community members and will consist of four weekly entry periods until July 14th, 2024. Click the image below to find out more on how you can win free tickets to #PPCC24 by entering the Summer of Solutions TODAY!   Microsoft Customer Stories We're constantly working with an array of great businesses across the globe to assist them in taking advantage of the latest business applications technology. If you'd like to find out more about their low code journeys, click the image below to view our playlist of Customer Stories to discover how Accenture, Lumen Technologies, Cineplex, and many more, are streamlining their business processes with Microsoft Power Platform.     Microsoft Leap Program Have you heard of Microsoft Leap - a global program designed to recruit, develop, and upskill unconventional talent for careers in the tech space. Microsoft Leap organizes a number of pathways into the industry, including the recent "NFL Legend Cohort - Technical Program Management" run jointly with the NFL Player Care Foundation (PCF) who are dedicated to helping retired players improve their quality of life. Click the image below to find out more about the great day shared at the Redmond campus and be sure to visit the Microsoft Leap website to discover how this amazing initiative is helping re-launch the lives of countless individuals. www.leap.microsoft.com       UPCOMING EVENTS Biz Apps Partner Summit | Seattle | July 24-25 It's not long now until the Biz Apps Partner Summit, which takes place at the Hilton Bellevue in Seattle on July 24-25, 2024. This event is the perfect place to network, connect, and learn how to scale your Microsoft practice, drive profitable revenue, and dazzle your customers! There's a great selection of speakers, including the likes of Tom Patterson, Donald Kossmann Joseph Corigliano, Cecilia Flombaum, Peter Jensen, John Siefert, Becky Lymberis, Daniel Rippey, and many more. Click the image below to find out more and register today!     TechCon365 & Power Platform Conference | D.C. | August 12-16 Things are hotting up for the next TechCon365 & PWRCON Conference in Washington D.C. on August 12-16, 2024. Featuring the likes of Tamara Bredemus, Sunny Eltepu, Lindsay Shelton, Brian Alderman, Daniel Glenn, Julie Turner, Jim Novak, John White, Jason Himmelstein, Luc Labelle, Emily Mancini, MVP, UXMC, Fabian Williams, Emma Wiehe,and many more, this is the perfect event for those that are looking to gain invaluable insights from industry experts. Click the image below to grab your tickets today!     Power Platform Community Conference | Vegas | Sept. 18-20th Are you ready to come and join the fun in Las Vegas this September at PPCC24? This event is the perfect place to connect with fellow business applications enthusiasts and share your knowledge with the worldwide Microsoft Community. Now's your chance to hold all the aces. Just click the image below to find out more and we hope to see you go ALL-IN this September in Las Vegas!     For more events, click the image below to visit the Community Days website.  

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

Top Solution Authors
Users online (2,292)