cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
jaimeS
New Member

URGENT- Sending email with PDF attachment

Hello! I have a flow that reads a code from a PDF, matches that code to an email address, and sends the email with the corresponding PDF attachment. So far, I have been moderately successful. However, on all of my test runs and regular runs, the flow will not generate all of the emails. In a Doc library of 8 PDFs, it only generated 6 emails. My Document folder contains 8 PDFs, my List contains 777 email addresses. I am unsure what may be causing the flow to not generate some emails. Many thanks in advance!

Document Library:

jaimeS_0-1700158838699.png

List:

jaimeS_1-1700158972638.png

Flow:

jaimeS_2-1700159065298.png   I used Get Items from my list and Get Files (properties only) from my Doc library 

jaimeS_4-1700159146550.png  I used Get Metadata to pull the file name from the PDF and then have a                                                                                                 condition that if the name contains the Code it creates the email.

jaimeS_6-1700159232622.png

jaimeS_7-1700159334152.png  The "To" section pulls from my List, the Attachments Name pulls from the                                                                                               Metadata, and the Attachments Content pulls from Get File Content

 

 

 

2 ACCEPTED SOLUTIONS

Accepted Solutions

@jaimeS The logic in your flow needs to be corrected. Your issue lies within these actions. 

 

The first Apply to Each action is looping through every file and you are using the Get File Metadata action—this action isn't necessary because you already have all the metadata from the Get Files (properties only) action. 

 

creativeopinion_0-1700166314228.png

 

Within the first Apply to each action loop you have another Apply to Each action looping through the value returned from the Get File Metadata action. 


Tip: Always rename your actions to keep things organized in your flow.

 

Filter Items/Files

If possible I would recommend you utilize the Filter Query in the Get Items and Get Files actions to reduce the number of items returned. I'm not sure if you have any parameters for the files that are returned. This would help ensure your flow is efficient.

 

Fun fact. The Get Files (properties only) returns folders as well. You need to use a Filter Query to return Files only. Refer to this YT Short.

Item Count

Whenever you use the Filter Query in your flow, I recommend adding a Compose action to count the number of items returned to ensure that the number of items returned is what you are expecting. This can help with troubleshooting.

 

Add a Compose action to store the count of items returned. Insert an expression. Use the length() function.

creativeopinion_1-1700169275888.png

Click on the Dynamic content tab and insert the outputs from the Get files (properties only) action) above.

creativeopinion_2-1700169292414.png

If you are using a Filter Query for the Get Items action, I'd recommend returning an item count for that action as well.

 

Run a test. Tip: Always run tests at each stage of your flow. This will help you to troubleshoot problems early on. 

creativeopinion_3-1700169400187.png

 

Top Count

Depending on how many files you have in your Doc Library, I would recommend limiting the Top Count to a smaller number than the total number of files in your Doc Library. This will increase the speed of your flow runs. Instead of returning all files—it'll limit the Get Files (properties only) action to the number entered here.

creativeopinion_4-1700169481181.png

 

Loop through each File

Use an Apply to Each action to loop through each file returned from the Get Files (properties only) action. 

creativeopinion_5-1700169515606.png

As mentioned at the start of this post the Get file metadata action is not required—it's redundant. 

 

Add a Compose action to store the name of the file. 

creativeopinion_6-1700169650846.png

Run a test. The Compose action should output the filename. 

creativeopinion_7-1700169745432.png

 

Compose Search String

You need to extract the text string from your file name that you are going to be using to cross-refrence with your SharePoint list.

 

Add a Compose action.

creativeopinion_12-1700170511550.png

Insert an expression. Use the split() function. 

creativeopinion_15-1700170579949.png

 

Select the dynamic content tab and insert the outputs from the Compose action above that contain your file name.

 

creativeopinion_14-1700170565322.png

 

Add a comma and an underscore between single quotes. 

creativeopinion_17-1700170678504.png

 

Run a test. The split() function will split the string of text by the delimiter you've specified—in this case an underscore. The Compose action will return an array of items. The first position of an array is [0], second is [1]... etc. 

creativeopinion_18-1700170744395.png

 

To return the second item you will need to make an adjustment to the expression. Append a [1] to the end of the expression. This will return the second item in the array.

creativeopinion_19-1700170820965.png

Run a test.

creativeopinion_20-1700170879043.png

Filter Out List Items

At the start of your flow you've already used the Get Items action to return the list of items from your SP list. Using a Condition action and an apply to each action to loop through each item returned from that action is not efficient and will take a long time for your flow to run. Instead you'll need to use a Filter Array action. To learn more about how to use the Filter Array action, please refer to this recent YT Tutorial I uploaded.

 

Add a Filter Array action into the Apply to Each action. In the From field insert the value dynamic content from the Get Items action.

 

creativeopinion_8-1700169932369.png

 

In the first value field, insert the Title dynamic content from the Get Items action.

creativeopinion_21-1700171003067.png

 

Change the operator to contains and in the second value field insert the outputs from the Compose action above. 

creativeopinion_22-1700171039135.png

 

The Filter Array action will filter out the items from your SharePoint list where the title contains the text from the Compose action above.

creativeopinion_23-1700171050266.png

 

Add an Item Count. Add a Compose action to store the count of items returned from your Filter Array action.

 

creativeopinion_10-1700170080864.png

creativeopinion_11-1700170105846.png

Run a test. 

 

Add Condition

Add a Condition action to check if the Filter Array returns any items. This will prevent the flow from failing if items aren't returned. You can change the condition to suit your needs. Ideally the Filter Array action should only return 1 item or none. 

 

Keep in mind, your Filter Array action is checking to see if the SP list title contains the string of text from the file name. It's not an exact match—unsure if there might be a chance that more than one SP item is returned. You'll have to troubleshoot and adjust your flow (if that occurs).

 

In the first value field I've inserted the outputs from the Compose action that is storing the length of items returned. I changed the operator to is not equal to and entered 0 into the second value field. 

 

All my actions will go into the YES branch. You can adjust this to suit your requirements/preferences.

creativeopinion_2-1700181574427.png

 

Get Dynamic Content from Filter Array

Take a look at the outputs from your Filter Array action. All dynamic content can be returned with an expression. You will need to know key for the content. The key is the text in red between the double quotes. Refer to this section of a YT Tutorial I uploaded on how to get dynamic content from a Filter Array action

creativeopinion_0-1700181524203.png

Add a Compose action and insert an expression. Start off with:

?[0]['']

The Filter Array will always return an array of items (even if there is a single item). You need to select that item by entering the key. The [0] will select the FIRST item in the array (assuming there is always a single item). If more than one item is returned in the Filter Array action—it'll only select the first item.

 

Insert the dynamic content key for the email column in between the single quotes. In my case it's

EmailAddress.

creativeopinion_9-1700182165733.png

 

 

 

Press the UP arrow key to go to the start of your expression and select the Dynamic Content tab. Insert the body dynamic content from the Filter Array action. 

creativeopinion_10-1700182184247.png

 

Run a test. Confirm the Compose action is returning the email address(es). 

creativeopinion_11-1700182244513.png

 

Get File Content

Add a Get file Content action and in the File Identifier field, insert the Identifier dynamic content from the Get Files (properties only) action.

creativeopinion_12-1700186309410.png

 

Send an Email

Add a Send an Email (V2) action to your flow. Tip: When building and testing a flow that involves sending an Email or posting a message in Teams, always send it to yourself—until you've confirmed the flow is working the way you intended it to work. 

 

I do like to add a line of text in the body of the email (or Teams message) that confirms who the email will be sent to. This is optional (not necessary).

 

You can customize the subject line to include dynamic content (if you'd like). For the Attachment Name, insert the File name with extension dynamic content from the Get files (properties only) action. 

 

In the Attachment Content field, insert the body dynamic content from the Get File content action. The from email address isn't necessary unless you are sending the email form a Shared mailbox.

creativeopinion_13-1700186418252.png

creativeopinion_14-1700186528019.png

 

Run a test. Once you've confirmed everything works you can adjust the trigger if you want and replace the recipient with the Compose action outputs that is storing the email addresses.

 

Hope this helps!


If I helped you solve your problem—please mark my post as a solution .
Consider giving me a 👍 if you liked my response!

👉Watch my tutorials on YouTube
👉Tips and Tricks on TikTok

View solution in original post

Sorry again! It was not as I thought it would be. I was afraid it would try to move the PDFs before they had been sent but I have it figured out. Thank you again so much for all of your help. This flow is saving a lot of people a lot of time and it is greatly appreciated!

View solution in original post

12 REPLIES 12

@jaimeS Have you turned on pagination and set a threshold in your Get Items action?

creativeopinion_0-1700160524593.png

 

creativeopinion_2-1700160557974.png

creativeopinion_1-1700160540126.png

If you don't turn on pagination and set a threshold, the Get Items action will not return all items.

 

You should also consider using a Filter Array action instead of nesting Apply to Each actions within each other. It would help your flow to run more efficiently. To learn more about how to use the Filter Array action, please refer to this recent YT Tutorial I uploaded.

 

Hope this helps!


If I helped you solve your problem—please mark my post as a solution .
Consider giving me a 👍 if you liked my response!

👉Watch my tutorials on YouTube
👉Tips and Tricks on TikTok

 

Good afternoon creativeopinion, thank you for your response. I turned on pagination for the Get Items and even for the Get Files, but I am still not getting all of the emails that should be generated. I just ran a test of 10 PDFs and it only generated 5 emails. 

@jaimeS The logic in your flow needs to be corrected. Your issue lies within these actions. 

 

The first Apply to Each action is looping through every file and you are using the Get File Metadata action—this action isn't necessary because you already have all the metadata from the Get Files (properties only) action. 

 

creativeopinion_0-1700166314228.png

 

Within the first Apply to each action loop you have another Apply to Each action looping through the value returned from the Get File Metadata action. 


Tip: Always rename your actions to keep things organized in your flow.

 

Filter Items/Files

If possible I would recommend you utilize the Filter Query in the Get Items and Get Files actions to reduce the number of items returned. I'm not sure if you have any parameters for the files that are returned. This would help ensure your flow is efficient.

 

Fun fact. The Get Files (properties only) returns folders as well. You need to use a Filter Query to return Files only. Refer to this YT Short.

Item Count

Whenever you use the Filter Query in your flow, I recommend adding a Compose action to count the number of items returned to ensure that the number of items returned is what you are expecting. This can help with troubleshooting.

 

Add a Compose action to store the count of items returned. Insert an expression. Use the length() function.

creativeopinion_1-1700169275888.png

Click on the Dynamic content tab and insert the outputs from the Get files (properties only) action) above.

creativeopinion_2-1700169292414.png

If you are using a Filter Query for the Get Items action, I'd recommend returning an item count for that action as well.

 

Run a test. Tip: Always run tests at each stage of your flow. This will help you to troubleshoot problems early on. 

creativeopinion_3-1700169400187.png

 

Top Count

Depending on how many files you have in your Doc Library, I would recommend limiting the Top Count to a smaller number than the total number of files in your Doc Library. This will increase the speed of your flow runs. Instead of returning all files—it'll limit the Get Files (properties only) action to the number entered here.

creativeopinion_4-1700169481181.png

 

Loop through each File

Use an Apply to Each action to loop through each file returned from the Get Files (properties only) action. 

creativeopinion_5-1700169515606.png

As mentioned at the start of this post the Get file metadata action is not required—it's redundant. 

 

Add a Compose action to store the name of the file. 

creativeopinion_6-1700169650846.png

Run a test. The Compose action should output the filename. 

creativeopinion_7-1700169745432.png

 

Compose Search String

You need to extract the text string from your file name that you are going to be using to cross-refrence with your SharePoint list.

 

Add a Compose action.

creativeopinion_12-1700170511550.png

Insert an expression. Use the split() function. 

creativeopinion_15-1700170579949.png

 

Select the dynamic content tab and insert the outputs from the Compose action above that contain your file name.

 

creativeopinion_14-1700170565322.png

 

Add a comma and an underscore between single quotes. 

creativeopinion_17-1700170678504.png

 

Run a test. The split() function will split the string of text by the delimiter you've specified—in this case an underscore. The Compose action will return an array of items. The first position of an array is [0], second is [1]... etc. 

creativeopinion_18-1700170744395.png

 

To return the second item you will need to make an adjustment to the expression. Append a [1] to the end of the expression. This will return the second item in the array.

creativeopinion_19-1700170820965.png

Run a test.

creativeopinion_20-1700170879043.png

Filter Out List Items

At the start of your flow you've already used the Get Items action to return the list of items from your SP list. Using a Condition action and an apply to each action to loop through each item returned from that action is not efficient and will take a long time for your flow to run. Instead you'll need to use a Filter Array action. To learn more about how to use the Filter Array action, please refer to this recent YT Tutorial I uploaded.

 

Add a Filter Array action into the Apply to Each action. In the From field insert the value dynamic content from the Get Items action.

 

creativeopinion_8-1700169932369.png

 

In the first value field, insert the Title dynamic content from the Get Items action.

creativeopinion_21-1700171003067.png

 

Change the operator to contains and in the second value field insert the outputs from the Compose action above. 

creativeopinion_22-1700171039135.png

 

The Filter Array action will filter out the items from your SharePoint list where the title contains the text from the Compose action above.

creativeopinion_23-1700171050266.png

 

Add an Item Count. Add a Compose action to store the count of items returned from your Filter Array action.

 

creativeopinion_10-1700170080864.png

creativeopinion_11-1700170105846.png

Run a test. 

 

Add Condition

Add a Condition action to check if the Filter Array returns any items. This will prevent the flow from failing if items aren't returned. You can change the condition to suit your needs. Ideally the Filter Array action should only return 1 item or none. 

 

Keep in mind, your Filter Array action is checking to see if the SP list title contains the string of text from the file name. It's not an exact match—unsure if there might be a chance that more than one SP item is returned. You'll have to troubleshoot and adjust your flow (if that occurs).

 

In the first value field I've inserted the outputs from the Compose action that is storing the length of items returned. I changed the operator to is not equal to and entered 0 into the second value field. 

 

All my actions will go into the YES branch. You can adjust this to suit your requirements/preferences.

creativeopinion_2-1700181574427.png

 

Get Dynamic Content from Filter Array

Take a look at the outputs from your Filter Array action. All dynamic content can be returned with an expression. You will need to know key for the content. The key is the text in red between the double quotes. Refer to this section of a YT Tutorial I uploaded on how to get dynamic content from a Filter Array action

creativeopinion_0-1700181524203.png

Add a Compose action and insert an expression. Start off with:

?[0]['']

The Filter Array will always return an array of items (even if there is a single item). You need to select that item by entering the key. The [0] will select the FIRST item in the array (assuming there is always a single item). If more than one item is returned in the Filter Array action—it'll only select the first item.

 

Insert the dynamic content key for the email column in between the single quotes. In my case it's

EmailAddress.

creativeopinion_9-1700182165733.png

 

 

 

Press the UP arrow key to go to the start of your expression and select the Dynamic Content tab. Insert the body dynamic content from the Filter Array action. 

creativeopinion_10-1700182184247.png

 

Run a test. Confirm the Compose action is returning the email address(es). 

creativeopinion_11-1700182244513.png

 

Get File Content

Add a Get file Content action and in the File Identifier field, insert the Identifier dynamic content from the Get Files (properties only) action.

creativeopinion_12-1700186309410.png

 

Send an Email

Add a Send an Email (V2) action to your flow. Tip: When building and testing a flow that involves sending an Email or posting a message in Teams, always send it to yourself—until you've confirmed the flow is working the way you intended it to work. 

 

I do like to add a line of text in the body of the email (or Teams message) that confirms who the email will be sent to. This is optional (not necessary).

 

You can customize the subject line to include dynamic content (if you'd like). For the Attachment Name, insert the File name with extension dynamic content from the Get files (properties only) action. 

 

In the Attachment Content field, insert the body dynamic content from the Get File content action. The from email address isn't necessary unless you are sending the email form a Shared mailbox.

creativeopinion_13-1700186418252.png

creativeopinion_14-1700186528019.png

 

Run a test. Once you've confirmed everything works you can adjust the trigger if you want and replace the recipient with the Compose action outputs that is storing the email addresses.

 

Hope this helps!


If I helped you solve your problem—please mark my post as a solution .
Consider giving me a 👍 if you liked my response!

👉Watch my tutorials on YouTube
👉Tips and Tricks on TikTok

So far so good. I can see the logic in creating the flow this way. Thank you for your time! Is this ready to send email or are there more steps? 

@jaimeS There is more. I've just added to the original post. Hope this helps.

This is great! But apparently I am not understanding the logic behind Get Items. I am getting Items from a List of codes with corresponding email addresses. The List is 777 unique rows. I thought I would then set the pagination for 800 to accommodate for additions. But even with the Top Count set at 10 I get an Item Count of 150. So it is emailing 150 of each file in my folder. What am I missing?

@jaimeS Setting the top count was to help speed up your flow runs while testing. In your case, because you need to look up the items in your SP list, you would only be setting the top count on the Get Files (properties only) action. This way you run the automation on a few files.. (while testing) rather than ALL the files. 

 

Hope that helps.

Okay, thank you. I'm sorry but I am not understanding this very well. I only have 10 files in my Document library. My Compose File Count shows 10 for the Output. But when I just ran another test, I am getting hundreds of emails. My Get Items is paginated at 800 with no top count now but my Compose Item Count shows an Output of 150. I know I'm doing something stupid but I'm not sure what. Thank you for your patience!

@jaimeS No worries. From what it sounds like, you must be looping through the SP items and not your files returned. 

 

You need to ensure that value dynamic content you've inserted into the Apply to Each action is from the Get files (properties only) action.

creativeopinion_0-1700194125230.png

creativeopinion_1-1700194153538.png

 

I see what I was doing wrong. In the To section of my email I had used the wrong dynamic content and it had created a second Apply To so it was creating the mass emails. I have however, discovered another issue. So far everything runs great but there are certain files that pass all the way to Compose File Name and the Outputs are correct. But certain ones are not passing the Filter array Items. The Outputs are Body [ ]. So I get a "ActionBranchingConditionNotSatisfied" error at Compose Email Addresses. I don't see any difference in the File Name as all of the PDFs are structured exactly the same. My Filter array Items has From = outputs('Get Items')?['body/value'] Value= item()?['Title'] contains outputs('Compose_Client_Name'). I'm just not sure why it is rejecting some files. If this an issues with the files, can I have something in the If no part of my condition that will identify these and skip them so that the flow doesn't break?

Lol! Sorry...I figured it out. I had the Filter array wrong. It all works like a charm! Thank you so much!! If I may please. beg one more favor...once a PDF emails, how would I move it from the source folder to a "processed" folder?

Sorry again! It was not as I thought it would be. I was afraid it would try to move the PDFs before they had been sent but I have it figured out. Thank you again so much for all of your help. This flow is saving a lot of people a lot of time and it is greatly appreciated!

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 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  

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 (972)