cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
JorisdG
Power Apps
Power Apps

ParseJSON feedback

It’s been roughly two months since we released ParseJSON as an experimental feature in Power Apps. A lot of scenarios for makers have been unblocked with this feature, and we’ve seen great uptake even though it’s still considered experimental. We’re anxious to get this out of that experimental status. I wanted to take the opportunity to highlight a recent improvement, and address feedback with some of the future plans we have once we take ParseJSON (and untyped objects) out of the experimental phase.

Finally, and most importantly, I’m asking for your feedback. I will elaborate below but if you’re using ParseJSON I would love to hear from you. We’ve seen comparatively low feedback given the amount of usage. This is probably a good sign, but it makes us a little nervous pushing to preview or GA without making sure there aren’t any issues we just haven’t heard about.

 

Update since experimental launch

You can now use ForAll(), like Index(), directly on an untyped object. A JSON object array such as [ { “id”: 1, “Title”: “One” }, { “id”: 2, “Title”: “Two” } ] would previously require a Table(ParseJSON()) call before going to ForAll. This has the added drawback of resulting in a single-column table with untyped objects, so you would get something like:

 

ForAll( Table(untypedObject), { id: Value(ThisRecord.Value.id) )

 

requiring you to use the .Value field on ThisRecord for the single-column table. You can now pass untyped objects directly into ForAll, which no longer creates a single-column table requiring the use of the Value column. So the previous example becomes:

 

ForAll( untypedObject, { id: Value(ThisRecord.id) )

 

 

Feedback so far

The feedback we’ve received so far is positive in that this feature unblocks many scenarios involving JSON. There are two recurring points of feedback we’ve heard from multiple customers:

 

  1. The feature is very “verbose” today due to the requirement of casting every field individually to a specific type. If you set a table of untyped objects as the Items source of a gallery, each use of a field requires Value(), Text() and other casting everywhere you wish to use the fields. For now you can consider using ForAll to type everything into a typed table first, as shown above, making field access easier. Our ultimate goal is to allow you to define your own type schemas and cast the whole JSON to it. We envision this feature to be used with the ParseJSON() function, where you pass in the JSON string as well as the type you defined, and the result of ParseJSON() would then be a typed object as opposed to an untyped object that requires casting. To be clear, we intend to GA ParseJSON with untyped objects first, and add the new typing features later on.

 

  1. Using ParseJSON() with connectors. If a column from a datasource contains a string with JSON, that is easy enough. But we’ve heard of scenarios where makers want to take the whole response message from a connector and manually parse the JSON when the app runs. The connector team is looking to build on top of our work with untyped objects, and beyond that also the previously mentioned type schema definitions to take connectors to a new level. The experimental Dynamic Schema feature is great but is missing some features and flexibility in Power Fx, and we’re starting to address those in Power Fx (with untyped objects and type definitions). There’s some short and long term work going on that I hope you will get to hear about soon.

 

If you have any feedback or concrete scenarios you’d like to share, I'd love it if you could comment on this thread. I would love to understand how you’re using ParseJSON or trying to use ParseJSON!

49 REPLIES 49
adrianoc
New Member

We have fed back internally through the partners we're working with on Microsoft Fast Track, but I wanted to reiterate here that this ParseJson function, even in its experimental form, is a huge improvement over existing patterns for consuming data from external APIs for display/processing in the app.

 

We have an app that is designed to allow users to search a third party API, and then that data can be used to fill out details on other records. Previously we used a Flow to call the API and the flow created records in a custom Dataverse table, and then we displayed the results in the app directly from table with a filter. That was extremely slow, mostly because it just took a long time to process the steps in the Flow. Returning the API response directly and displaying it with Table(ParseJson()) gave a massive boost to performance.

 

I will say that the syntax feels a little obscure/strained to me, especially with lots of nested JSON from a Graphql query (for example) needing chained Index()es , but I am not a Canvas App expert -- this is the first time I've ever seen Canvas Apps -- so this feeling might be my lack of understanding of the design goals for this tool. I notice you've updated this post to say that the type casting requirements have been improved, but I actually didn't mind the explicit casts, I felt they made it a little clearer to scan what was going on in the data.

 

I would love to see this function move out of experimental and into preview, we'd very much like to use this feature more widely.

rodneyb
Frequent Visitor

This feature opened up a whole range of capabilities for me as I use a single PCF to request commands and return json.

 

One blocker that has come up just now is what seems to be this: If the ParseJson call used to populate a collection, it does not appear to be completed when, say, a Navigate is called immediately after. I get the collection but only one row with the value "true" populated in a new column called "Value". If I eliminate the navigation, it builds the collection fine (I've been using ParseJSON quite extensively for the last month).

 

Is the ParseJson in fact an asynchronous operation? Thanks, Rodney

 

P.S. This issue only shows up after publishing and viewing on an android tablet or phone. Editing or playing on the desktop does not exhibit the issue (not sure about apple).

Are you using Collect() or ClearCollect() to populate the collection? And on mobile you're using the main Power Apps app I assume?

rodneyb
Frequent Visitor

Yes, ClearCollect. I'm not sure what you mean when you mention "main Power Apps app". Do you mean as opposed to a direct url?

 

As an aside, I have noticed that most connectors or actions seem to be asynchronous. Unless, for example, I check for, say, the result of a Flow. Then the code waits and I'm able to check result success. In fact, to counter that behavior when I want speed but need stuff to wait on other stuff, I created a queue system so Flow calls (and results checked) happen in a separate thread.

 

Here's the code just before I call Navigate. The next screen's data call only works (99% of the time) because, on the next screen I implement a 200ms delay with a Timer. It's notable, too I think, that, without the Timer or any other hack, the data on the next screen will load correctly every time after the first navigation back/forth. As if it needed a one-time cache to load:

 

      ClearCollect(collAllProductsZASSLocations, 
        ForAll( ParseJSON( actionslocationsdata ) , 
        { 
            sProductName: Text(ThisRecord.Value.sProduct), 
            sCount: Value(ThisRecord.Value.sCount),
            iProductID: Value(ThisRecord.Value.iProductID) 
        });
        //UpdateContext({startDelay:true})
         //Notify("naving", Success, 4000);
         Navigate(screenAllZASSLocations)

 

Let me know if that doesn't make sense.

 

 

 

Thanks, Rodney

PavelSheludkov
Advocate I
Advocate I

Just gave this feature a go while evaluating an SQL On-Prem integration scenario.

It works well and allow to easily parse flow response that running a stored procedure to obtain required data.

Any updates on when ParseJSON feature is going to move to Preview?

LaelLeeH
Helper II
Helper II

Hi @JorisdG 

I have until now been using Match and MatchAll to manually parse json strings. I recently started swapping over to ParseJSON and so far so good, but I am now battling with a nested JSON array of records.

My Match statement was:

LaelLeeH_0-1674101747987.png

 ... where the last field ProcessPerformersJSON, is a nested JSON array of records which I Parse at a later date into another collection

My new ParseJSON looks as follows:

LaelLeeH_1-1674101826956.png

But that last conversion is throwing an error:

LaelLeeH_2-1674107531301.png

I have tried replacing Text(ThisRecord.Value.ProcessPerformersJSON) with  Table(ThisRecord.Value.ProcessPerformersJSON) and with Text(ThisRecord.ProcessPerformersJSON) and with an entire ForAll to Parse the nested table and I can't get anything to work. 

 

I can send you a copy of my incoming JSON string privately if necessary.

Any assistance you can provide will be greatly appreciated.

Thanks

Regards

Lael

 

LaelLeeH
Helper II
Helper II

Hi @JorisdG 

I have another scenario where I have been using string manipulation up until now, and it works perfectly but it is ugly and I am sure it is not too performant either.  I would love to replace it with ParseJSON if possible.  However, the JSON field name is dynamic (or passed in to the string manipulation as a parameter) and I am not sure if this is possible with ParseJSON.

 

My current manipulation looks something like this. See InputValue: in the code below:

ClearCollect(

            colFormFields,

            AddColumns(

                        colMyHeaderAttributes,

                "InputValue",

                                                    Mid(

                                                        First(

                                                            Split(

                                                                Mid(

                                                                    _lSelectedTransaction.jsonCol,

                                                                    Coalesce(

                                                                        Find(

                                                                            """" & jsonName & """:",

                                                                            _lSelectedTransaction.jsonCol

                                                                        ),

                                                                        99999999

                                                                    ),

                                                                    Len(_lSelectedTransaction.jsonCol)

                                                                ),

                                                                ","""

                                                            )

                                                        ).Result,

                                                        Find(

                                                            ":",

                                                            First(

                                                                Split(

                                                                    Mid(

                                                                        _lSelectedTransaction.jsonCol,

                                                                        Coalesce(

                                                                            Find(

                                                                                """" & jsonName & """:",

                                                                                _lSelectedTransaction.jsonCol

                                                                            ),

                                                                            99999999

                                                                        ),

                                                                        Len(_lSelectedTransaction.jsonCol)

                                                                    ),

                                                                    ","""

                                                                )

                                                            ).Result

                                                        ) + 1,

                                                        (Len(

                                                            First(

                                                                Split(

                                                                    Mid(

                                                                        _lSelectedTransaction.jsonCol,

                                                                        Coalesce(

                                                                            Find(

                                                                                """" & jsonName & """:",

                                                                                _lSelectedTransaction.jsonCol

                                                                            ),

                                                                            99999999

                                                                        ),

                                                                        Len(_lSelectedTransaction.jsonCol)

                                                                    ),

                                                                    ","""

                                                                )

                                                            ).Result

                                                        ))

                                                    )

jsonName  refers to a field in colMyHeaderAttributes, and so is dynamic per record being added to the collection

Also, _lSelectedTransaction.jsonCol is not a unique json structure.  I have multiple different 'Transaction' types all configured with different jsonCol field naming structures, and hence the need to look up the jsonName in colMyHeaderAttributes

 

I have been trying to replace the above with something like this:

InputValue : Text(ParseJSON(_lSelectedTransaction.jsonCol).@jsonName)

or 

InputValue : Text(ParseJSON(_lSelectedTransaction.jsonCol).colMyHeaderAttributes[@jsonName])

Obviously both fail, and I totally understand why.  Is what I am trying to do possible by some other means?  It will make a massive difference to my app if I can get it to work. 

Thanks, in the sincere hopes of a successful outcome 😉

Regards

Lael

LaelLeeH
Helper II
Helper II

Hi @JorisdG 

 

Are you able to have a look at my two issues below and respond.  Getting them working will allow me to make some significant performance improvements to my app which are very sorely needed.  Will really appreciate a response.

 

Many thanks

Regards

Lael

JorisdG
Power Apps
Power Apps

Sorry for the late reply. Unfortunately we don't have a way to access a property by its name dynamically. It's something we've discussed in the past but we have no designs or anything on the roadmap at the moment.

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 in the Forums 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 of SolutionsSuper UsersNumber of Solutions @anandm08  23 @WarrenBelz  31 @DBO_DV  10 @Amik  19 AmínAA 6 @mmbr1606  12 @rzuber  4 @happyume  7 @Giraldoj  3@ANB 6 (tie)   @SpongYe  6 (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. Community MembersSolutionsSuper UsersSolutions @anandm08  10@WarrenBelz 25 @DBO_DV  6@mmbr1606 14 @AmínAA 4 @Amik  12 @royg  3 @ANB  10 @AllanDeCastro  2 @SunilPashikanti  5 @Michaelfp  2 @FLMike  5 @eduardo_izzo  2   Meekou 2   @rzuber  2   @Velegandla  2     @PowerPlatform-P  2   @Micaiah  2     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 Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27  

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

Users online (2,110)