cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

Power App generating PDF with duplicate data from htmlText control

Hello,

I have built an app that connects to multiple SharePoint lists - these are all served up into galleries and all connect really well in the app to the point that it functions as intended.


On the cases screen, we have a list of buildings in the left side gallery. On the Top right we have a form control that has fields for the building that shows data when a building from the buildings gallery is selected.
On the bottom right we have a list of topics - using the New topic button takes you to another screen where you can create new topics - these are linked to the building.

sudosaurus_0-1699558655432.png
As said above, here we have the other screen where we can view an existing selected topic (from the above screen) or create a new topic. On the top right, we have a list of Subtopics which are associated with each topic and the same building. On the bottom right, we can view the Subtopic information, which includes the Subtopic, Subtopic Breakdown, RAG Status, Argument and Evidence. Makes sense so far??
sudosaurus_1-1699558718389.png

Back on the Cases screen where we had the list of buildings on the left you will have seen the 'Create PDF' button:

sudosaurus_2-1699559087191.png

When selected, this starts off the process that will ultimately generate a PDF file via Power Automate.

The OnSelect property of the 'Create PDF' button is set to:

// Set your variables first
Set(varItem, ThisItem);
Set(varBuildingPhoto, LookUp(BuildingPhotos, Title = ThisItem.spBuilding).'Link to item');
Set(varBuildingPhotoID, LookUp(BuildingPhotos, Title = ThisItem.spBuilding).ID);

// Data collection and ClearCollect statements go here

// THIS INCLUDES ALL THE TOPIC HEADERS
ClearCollect(colSubtopics1, Distinct(Filter(SubtopicArgEvi_1,Building=varItem.spBuilding),Topic));

// THIS IS THE DISTINCT COLLECTION OF ORDER OF TOPICS
ClearCollect(colSubtopics, ForAll(Sequence(CountRows(colSubtopics1)), Patch(Last(FirstN(colSubtopics1,Value)),{Order:Value})));

ClearCollect(colTempAllSubtopics, AddColumns(Filter(SubtopicArgEvi_1,Building=varItem.spBuilding),"TopicOrder",0,"SubtopicOrder",0));
Clear(colTempAllSubtopicsB);
ForAll(colTempAllSubtopics, Collect(colTempAllSubtopicsB, {
    Top: colTempAllSubtopics[@Topic], 
    SubTop: colTempAllSubtopics[@Subtopic] & " - " & colTempAllSubtopics[@'Subtopic Breakdown'],
    Arg: colTempAllSubtopics[@Argument],
    Evid: colTempAllSubtopics[@Evidence],
    TopOrder: LookUp(colSubtopics,Value=colTempAllSubtopics[@Topic]).Order+2
}));

Clear(colAllSubtopics);

    Collect(colAllSubtopics, ForAll(Sequence(CountRows(Filter(colTempAllSubtopicsB, TopOrder=3)), 3.1, 0.1), Patch(Last(FirstN(Filter(colTempAllSubtopicsB, TopOrder=3), Value)), {SubTopOrder: RoundUp(Value, 2)})));
    Collect(colAllSubtopics, ForAll(Sequence(CountRows(Filter(colTempAllSubtopicsB, TopOrder=4)), 4.1, 0.1), Patch(Last(FirstN(Filter(colTempAllSubtopicsB, TopOrder=4), Value)), {SubTopOrder: RoundUp(Value, 2)})));
    Collect(colAllSubtopics, ForAll(Sequence(CountRows(Filter(colTempAllSubtopicsB, TopOrder=5)), 5.1, 0.1), Patch(Last(FirstN(Filter(colTempAllSubtopicsB, TopOrder=5), Value)), {SubTopOrder: RoundUp(Value, 2)})));
    Collect(colAllSubtopics, ForAll(Sequence(CountRows(Filter(colTempAllSubtopicsB, TopOrder=6)), 6.1, 0.1), Patch(Last(FirstN(Filter(colTempAllSubtopicsB, TopOrder=6), Value)), {SubTopOrder: RoundUp(Value, 2)})));
    Collect(colAllSubtopics, ForAll(Sequence(CountRows(Filter(colTempAllSubtopicsB, TopOrder=7)), 7.1, 0.1), Patch(Last(FirstN(Filter(colTempAllSubtopicsB, TopOrder=7), Value)), {SubTopOrder: RoundUp(Value, 2)})));
    Collect(colAllSubtopics, ForAll(Sequence(CountRows(Filter(colTempAllSubtopicsB, TopOrder=8)), 8.1, 0.1), Patch(Last(FirstN(Filter(colTempAllSubtopicsB, TopOrder=8), Value)), {SubTopOrder: RoundUp(Value, 2)})));
    Collect(colAllSubtopics, ForAll(Sequence(CountRows(Filter(colTempAllSubtopicsB, TopOrder=9)), 9.1, 0.1), Patch(Last(FirstN(Filter(colTempAllSubtopicsB, TopOrder=9), Value)), {SubTopOrder: RoundUp(Value, 2)})));
    Collect(colAllSubtopics, ForAll(Sequence(CountRows(Filter(colTempAllSubtopicsB, TopOrder=10)), 10.1, 0.1), Patch(Last(FirstN(Filter(colTempAllSubtopicsB, TopOrder=10), Value)), {SubTopOrder: RoundUp(Value, 2)})));

UpdateContext({IsLoading: true})

Where UpdateContext({IsLoading: true}) will display a modal dialog - which in this case is a set of controls in a container with a drop shadow to give the appearance of a modal dialog:

sudosaurus_4-1699559279259.png

This modal dialog is a combo of a spinner svg and a timer that counts down from 60,000 milliseconds.


The OnTimerStart property is set to the following: (and allows the above collections to collect data from the various data sources to avoid data being missing from the generated PDF file - this was previously happening and hence why I implemented the timer functionality)

// Trigger the workflow when data is ready
'BSC-PowerApps-v2'.Run(htmlBody_1.HtmlText, varBuildingPhoto, Now(), varBuildingPhotoID, htmlBody_2.HtmlText, htmlBody_3.HtmlText, varItem.ID;)

The OnTimerEnd property is set to the following:

Refresh(DocData);
Set(IsLoading, false); // This will hide the spinner
UpdateContext({IsLoading: false})

 

It's worth noting what the backend code is used for in the three htmlBody htmlText controls in the app - as these are outputting the main HTML static template as well as dynamic information from the datasources/collections into the PDF:

 

varBody1 / htmlBody_1

<h2><font color=blue>BUILDING SAFETY CASE REPORT HEADINGS</font></h2>
<h3>COVER PAGE</h3> 
•Name and address of property: "&LookUp(Buildings,Title=varItem.spBuilding).Title & ", " &LookUp(Buildings,Title=varItem.spBuilding).Address   &"<br>
•National UPRN: "&LookUp(Buildings,Title=varItem.spBuilding).NatUPRN & "<br>
•LiveWest UPRN: "&LookUp(Buildings,Title=varItem.spBuilding).CxUPRN & "<br>
•BSR Code: "&LookUp(Buildings,Title=varItem.spBuilding).BSRAppNo & "<br>
"

varBody2 / htmlBody_2

"
<h3>CONTENTS PAGE</h3>
<h3>1.DOCUMENT CONTROL AND EXECUTIVE SUMMARY</h3>
1.1.Document control table: Test data<br> 
1.2.Executive summary with overarching claim, argument, and RAG rating<br><br>
"&LookUp(DocData,spBuilding=varItem.spBuilding).spSummary & "

<h3>2.GENERAL INFORMATION</h3>
2.1.Building name and address: "&LookUp(Buildings,Title=varItem.spBuilding).Title & ", " &LookUp(Buildings,Title=varItem.spBuilding).Address   &"<br>
2.2.Location and site description<br>
2.3.Relevant persons<br>
2.3.1. Building owner: "&LookUp(Buildings,Title=varItem.spBuilding).'Building Owner' & "<br>
2.3.2. Accountable person: "&LookUp(Buildings,Title=varItem.spBuilding).'Principal Accountable Person' & "<br>
2.3.3. Other accountable persons: "&LookUp(Buildings,Title=varItem.spBuilding).'Other Accountable Persons' & "<br>
2.3.4. Responsible persons<br>
2.3.4.1.Head of Building Safety: "&LookUp(Buildings,Title=varItem.spBuilding).'Head of Building Safety' & "<br>
2.3.4.2.Fire Safety Manager: "&LookUp(Buildings,Title=varItem.spBuilding).'Responsible Persons Under Fire Safety' & "<br>
2.3.4.3.Other responsible persons: "&LookUp(Buildings,Title=varItem.spBuilding).'Other Responsible Persons' & "<br>
2.4.The building<br>
2.4.1. Description of the building: "&LookUp(Buildings,Title=varItem.spBuilding).'Category of Provision' & "<br>
2.4.2. Design and construction: Test data<br> 
2.4.3. Refurbishments: Test data<br>
2.4.4.   Additional photos: Test data<br>

varBody3 / htmlBody_3 (this one seems to be where the issue is)

"
2.4.5. Floor plans: Test data<br>
2.4.6. Elevation plans: Test data<br>
2.4.7. Description of the site: Test data<br>
2.4.8. Site plan and map: Test data<br>
2.4.9. Utilities: Test data<br>
2.4.10. Resident profile: Test data<br>


<table>
"&

Concat(colSubtopics,
"<tr><td><H3>"& Order+2 &" " & Value&"</H3>
<table>
<tr><td><b>Claim</b></td></tr>
<tr><td>"&LookUp(TopicsClaims,Building=varItem.spBuilding).Claim&"</td?></tr>
"
&
Concat(Filter(colAllSubtopics,TopOrder=Order+2),
"<tr><td><H4>"& SubTopOrder & "  " & SubTop &"</H4></td></tr>

<tr><td><b>Argument</b></td></tr>
<tr><td>"&Arg&"<br><br></td></tr>
<tr><td><b>Evidence</b></td></tr>
<tr><td>"&Evid&"<br><br></td></tr>
"



)
    
    
&


"





</table>




</td></tr>"


)

&"
</table>

<h3>"& Value(Last(colSubtopics).Order+3) &". ONGOING WORKS AND IMPROVEMENTS (all free text)</h3>
"& Value(Last(colSubtopics).Order+3) &".1.External wall remediation programme<br>
"& Value(Last(colSubtopics).Order+3) &".2.Fire Risk Assessment actions<br>
"& Value(Last(colSubtopics).Order+3) &".3.Fire door works<br>
"& Value(Last(colSubtopics).Order+3) &".4.Internal compartmentation works<br>
<h3>"& Value(Last(colSubtopics).Order+4) &". THE BUILDING SAFETY CASE (all free text)</h3>
"& Value(Last(colSubtopics).Order+4) &".1.How evidence is provided for the Building Safety Case Report<br>
<h3>"& Value(Last(colSubtopics).Order+5) &". REVIEWING AND UPDATING THE BUILDING SAFETY CASE AND REPORT</h3>
<h3>"& Value(Last(colSubtopics).Order+6) &". CLOSING STATEMENT AND SIGN OFF BOX</h3>


<br><br>
<b>Cover Page</b> <br><br>
<table border='1' style='border: 1px solid black; border-collapse: collapse'>
<tr><td width='200px'>DATE OF REPORT:</td><td width='450px'>"&Text(Today(),"dd/mm/yyyy")&"</td></tr>
<tr><td>VERSION:</td><td>1.0</td></tr>
<tr><td>BSR CODE:</td><td>"&LookUp(Buildings,Title=varItem.spBuilding).BSRAppNo&"</td></tr>
<tr><td>NATIONAL UPRN:</td><td>"&LookUp(Buildings,Title=varItem.spBuilding).NatUPRN&"</td></tr>
<tr><td>LIVEWEST UPRN:</td><td>"&LookUp(Buildings,Title=varItem.spBuilding).CxUPRN&"</td></tr>
<tr><td>PREPARED BY:</td><td>"&varItem.'Created By'.DisplayName&"</td></tr>
<tr><td>APPROVED BY:</td><td>Test data</td></tr>


</table>

<br><br>
<b>Version Control</b> <br><br>
<table border='1' style='border: 1px solid black; border-collapse: collapse'>

<tr style='background-color:#efefef'><th>Version</th><th>Date</th><th>By Whom?</th><th>Reason</th></tr>
<tr><td width='100px' style='text-align:center'>1.0</td><td width='100px' style='text-align:center'>"&Text(Today(),"dd/mm/yyyy")&"</td><td width='200px' style='text-align:center'>"&varItem.'Created By'.DisplayName&"</td><td width='250px'>Test data</td></tr>

</table>

 

Now it's worth noting that the issue seems to be with varBody3 / htmlBody_3 as the data is displayed correctly in the Outputs of the Power Automate flow trigger - PowerApps (V2).

Here's an example of a recent output:

2.4.5.	 Floor plans: Test data<br>
2.4.6.	 Elevation plans: Test data<br>
2.4.7.	 Description of the site: Test data<br>
2.4.8.	 Site plan and map: Test data<br>
2.4.9.	 Utilities: Test data<br>
2.4.10.	 Resident profile: Test data<br>


<table>
<tr><td><H3>3 Fire Safety</H3>
<table>
<tr><td><b>Claim</b></td></tr>
<tr><td>The Claim for fire safety is we carry out regulatory checks on a regular basis</td?></tr>
<tr><td><H4>3.1  Emergency Information - Evacuation Procedure</H4></td></tr>

<tr><td><b>Argument</b></td></tr>
<tr><td>we have an evac plan these are held centrally at head office and copies are in each building<br><br></td></tr>
<tr><td><b>Evidence</b></td></tr>
<tr><td>S:\ASSET MANAGEMENT\Fire Safety Team\Premises Registers PEEPs and PCFRAs<br><br></td></tr>
<tr><td><H4>3.2  Emergency Information - Evacuation Procedure</H4></td></tr>

<tr><td><b>Argument</b></td></tr>
<tr><td>we have an evac plan these are held centrally at head office and copies are in each building<br><br></td></tr>
<tr><td><b>Evidence</b></td></tr>
<tr><td>S:\ASSET MANAGEMENT\Fire Safety Team\Premises Registers PEEPs and PCFRAs<br><br></td></tr>
<tr><td><H4>3.3  Emergency Information - Evacuation Procedure</H4></td></tr>

<tr><td><b>Argument</b></td></tr>
<tr><td>we have an evac plan these are held centrally at head office and copies are in each building<br><br></td></tr>
<tr><td><b>Evidence</b></td></tr>
<tr><td>S:\ASSET MANAGEMENT\Fire Safety Team\Premises Registers PEEPs and PCFRAs<br><br></td></tr>






</table>




</td></tr><tr><td><H3>4 Structural Safety</H3>
<table>
<tr><td><b>Claim</b></td></tr>
<tr><td>The Claim for fire safety is we carry out regulatory checks on a regular basis</td?></tr>
<tr><td><H4>4.1  Building Information - Completion Certificates (Building Control & PC)</H4></td></tr>

<tr><td><b>Argument</b></td></tr>
<tr><td>this will see if the report can show more multiple subtopics against a topic<br><br></td></tr>
<tr><td><b>Evidence</b></td></tr>
<tr><td>Hope this works this test will say so<br><br></td></tr>
<tr><td><H4>4.2  Building Information - Completion Certificates (Building Control & PC)</H4></td></tr>

<tr><td><b>Argument</b></td></tr>
<tr><td>this will see if the report can show more multiple subtopics against a topic<br><br></td></tr>
<tr><td><b>Evidence</b></td></tr>
<tr><td>Hope this works this test will say so<br><br></td></tr>






</table>




</td></tr><tr><td><H3>5 Resident Engagement</H3>
<table>
<tr><td><b>Claim</b></td></tr>
<tr><td>The Claim for fire safety is we carry out regulatory checks on a regular basis</td?></tr>
<tr><td><H4>5.1  Resident Engagement Strategy - BEING DEVELOPED. Including Customer Consultation/Engagement, Managing Fire Safety Concerns, LW Fire Safety Standard Information & Home User Guide</H4></td></tr>

<tr><td><b>Argument</b></td></tr>
<tr><td>this information added after v37 so should appear in version v38 time stamp 16:09<br><br></td></tr>
<tr><td><b>Evidence</b></td></tr>
<tr><td>The evidence will be that this works hip hip hurray<br><br></td></tr>






</table>




</td></tr>
</table>

<h3>6. ONGOING WORKS AND IMPROVEMENTS (all free text)</h3>
6.1.	External wall remediation programme<br>
6.2.	Fire Risk Assessment actions<br>
6.3.	Fire door works<br>
6.4.	Internal compartmentation works<br>
<h3>7. THE BUILDING SAFETY CASE (all free text)</h3>
7.1.	How evidence is provided for the Building Safety Case Report<br>
<h3>8. REVIEWING AND UPDATING THE BUILDING SAFETY CASE AND REPORT</h3>
<h3>9. CLOSING STATEMENT AND SIGN OFF BOX</h3>


<br><br>
<b>Cover Page</b> <br><br>
<table border='1' style='border: 1px solid black; border-collapse: collapse'>
<tr><td width='200px'>DATE OF REPORT:</td><td width='450px'>09/11/2023</td></tr>
<tr><td>VERSION:</td><td>1.0</td></tr>
<tr><td>BSR CODE:</td><td>001</td></tr>
<tr><td>NATIONAL UPRN:</td><td>348114</td></tr>
<tr><td>LIVEWEST UPRN:</td><td>100426572</td></tr>
<tr><td>PREPARED BY:</td><td>Taiwo Adoti</td></tr>
<tr><td>APPROVED BY:</td><td>Test data</td></tr>


</table>

<br><br>
<b>Version Control</b> <br><br>
<table border='1' style='border: 1px solid black; border-collapse: collapse'>

<tr style='background-color:#efefef'><th>Version</th><th>Date</th><th>By Whom?</th><th>Reason</th></tr>
<tr><td width='100px' style='text-align:center'>1.0</td><td width='100px' style='text-align:center'>09/11/2023</td><td width='200px' style='text-align:center'>Taiwo Adoti</td><td width='250px'>Test data</td></tr>

</table>

and in the PDF this repeating bit of data displays as this:

sudosaurus_5-1699560150039.png

There's no need to display the Power Automate workflow as the data is being processed incorrectly in the app and outputted in an incorrect way in the initial flow trigger.

 

I appreciate all of this is a longshot however I've tried to detail everything as much as I can.

 

Appreciate any help with this.

 

Thanks!

Chris 🙂



If I helped you solve your problem - please mark my post as a solution and consider giving me a like if you liked my response!

If you're feeling generous you can Buy me a coffee: https://www.buymeacoffee.com/sudosaurus
0 REPLIES 0

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

We are excited to announce the Summer of Solutions Challenge!   This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions 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     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 Apps DBO-DV21WarranBelz26Giraldoj7mmbr160618Muzammmil_0695067Amik14samfawzi_acml6FLMike12tzuber6ANB8   SunilPashikanti8

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Users online (1,416)