Send email to multiple recipients in one go with Dataverse connector using Power Automate

In today's fast-paced digital world, effective communication is paramount. Whether you're coordinating with team members, reaching out to clients, or disseminating important information, sending emails efficiently can save you time and streamline your workflow. One powerful tool that can help you achieve this is Power Automate, Microsoft's cloud-based service that allows you to automate workflows across various applications and services.

In this blog post, we'll delve into how you can leverage the Dataverse connector within Power Automate to send emails to multiple recipients in one go, simplifying your email communication process and boosting your productivity.


    Fig.1

 Understanding Activity Party Attributes

An activity party in Power Apps is typically associated with various attributes that define the role and identity of the participants. Here's a breakdown of key attributes you might encounter:

 

Attributes of Activity Party:

PartyId: This attribute stores the ID of the party involved in the activity. It can be a user, contact, account, or any other entity type.

ParticipationTypeMask: This attribute indicates the role of the party in the activity. For example, it specifies whether the party is a sender, recipient, required attendee, etc.

ActivityId: This attribute links the activity party to the specific activity (e.g., an email, appointment).

Common Participation Type Masks

These are some of the common participation type masks you'll encounter:

1: Sender

2: Recipient

3: CC Recipient

4: BCC Recipient

5: Required Attendee

6: Optional Attendee

7: Organizer

8: Regarding

 

While using Email Messages entity for sending email using power automate, it will ask for the Activity party name and Activity party value.

It can be either selected from dropdown or given as JSON schema.


        Fig.2

 

To send email to multiple recipients follow the steps below.

Step 1:

We are going for the List Rows to get all the Users.


                Fig.3

 

 Step 2:

Once all the Users are listed, we must pass the GUID of all users into an array so that the array can used for sending email.

 

If multiple recipients are there, we must go for the JSON schema method.

The syntax of JSON schema is as follows:

{

  "participationtypemask": 2,

  "partyid@odata.bind": "systemusers(<GUID>)"

}

 


       Fig.4

Step 3:

Now the variable holds the information of all the users to whom the email must be sent.

This array variable can be used in the Email Messages Step

 

 


    Fig.5

 

One the trigger condition is met, the flow fetches all the users and passes the user GUID to the array variable. And the email is sent to all users in a go.


        Fig.6

 

Comments

Post a Comment

Popular posts from this blog

Create HTML table by combining columns from multiple entities

Image
Creating an HTML table in Power Automate is a very commonly used action. Building the HTML table using attributes from a single entity is quite simple and straightforward. However, when it comes to including columns from multiple entities, it requires some extra brainstorming! First, let’s understand how the "Create HTML Table" step works. The "Create HTML Table" step expects an array of objects in the From column. It provides the option to add static table column headers and dynamic table contents. Alternatively, you can let the system handle it automatically. In our case, we are going to create an HTML table by selecting columns from both the Contact and Account entities. From Contact , I will choose the First Name , Last Name , and Email fields, while the Company field will come from the Account entity. Since the "Create HTML Table" step expects an array of objects, we need to create the array with the required fields. To obtain the company name,
Read more

Dynamics 365 CRM Form Switching: A Deep Dive into formSelector and navigate()

Image
In the dynamic landscape of Dynamics 365 Customer Relationship Management (CRM), the ability to present different forms to various user groups based on specific conditions is a common and powerful customization requirement. Fortunately, the formSelector object, coupled with the navigate() function, provides an elegant solution to this challenge, allowing for seamless form switching based on user roles and other criteria. FormSelector Object At the heart of this functionality lies the formSelector object, a JavaScript object that acts as a gateway to managing forms within Dynamics 365 CRM. The formSelector object grants access to a collection of items, representing all the forms accessible to the current user. It's important to note that these forms are filtered based on the user's security roles, ensuring a secure and controlled form-switching experience. Exploring the items Collection Within the formSelector object, the items collection stands out as a crucial repository
Read more

Create and Send Emails with Attachments in D365/Dataverse with Power Automate

Image
  With Power Automate, you can connect to over 300 connectors, including the Outlook connector that can send emails, which is great. However, if you are used to working with Dynamics 365 or Dataverse, one of the key advantages is tracking emails, and if you use the Outlook connector, you cannot do this. This post will show how to create an email, how to add an attachment and how to send an email, so that it’s tracked inside of D365/Dataverse. Create a file or attachment that you want to add onto an email, in my example, I'm going to carry on from my previous post about Word Templates. Then we will "Add a new row" using the Dataverse Connector and the Table name will be Email Message. This will create an email record/row in D365 which requires certain parameters. Firstly, the way email fields to, cc, bcc and from work in D365/Dataverse is via what is called an activity party list. This is a list of rows/GUIDs of rows inside of D365/Dataverse that the email message is conn
Read more