This article demonstrates steps to export Entra ID groups with members details in csv format. 

How to use Power Automate Desktop to send an Excel table, including cell colours, through Outlook. This can be particularly useful when you want to share data in a visually appealing and easy-to-understand format.

The Power Platform empowers makers with prebuilt AI prompts for generating AI-driven responses in Power Automate flows and Power Apps, which can be utilized in common business scenarios such as summarizing, classifying, extracting data, translating, assessing sentiment, or drafting a reply.

Copilot in Power Automate enables you to describe a flow you wish to create from scratch and also provides assistance in enhancing and modifying your existing flows.

Check out my post to get target or actual link of a file from the shortcut link (.url) in SharePoint library!

To Convert the Word to PDF you have to follow the below:

1. As shown below, create the document in OneDrive if it is not already there.
2. Call the OneDrive File Convert step, pass the file ID from the previous step, and select PDF as the conversion type.

If this post helps you with your problem, please give it a Thumbs Up. 

#PowerAutomate #Word_Template #Download_Word_Templates #Model_Driven_APP

For UAT testing

One of the big challenges of understanding why your failed is reading the error message, this one minute fix will show you how to always get the right error message

Connect to Azure OpenAI Whisper API in Power Automate

Using environment variables for a smoother deployment of PA Flows with a dataflow trigger.

Often times there are requests to append file names with a timestamp, customerID, or another identifier when files are created in SharePoint Libraries. This short flow will show you how to do it, step by step.  We will add the date in the following format MM-dd-yyyy to the file name.

There are many reasons a Outlook trigger wont find but I have found a common issues when promoting flows between environments with different mailboxes.

Have you ever wondered how to automate repetitive chores with Power Automate? You're not by yourself! This article is your one-stop shop for learning the fundamentals before creating your first flow.

Let's take it apart:

1. The Spark: Triggers

Think of a trigger as your flow's starting pistol. It is a triggering event.

Examples include receiving a new email, uploading a file to OneDrive, at a specific time interval and seeing a tweet with a specific hashtag.

Think of this: When a new sales leader appears in your CRM, a flow is triggered. The lead is then automatically emailed a welcome message!

2. Actions

Actions are the backbones of your flow. They are the specific actions that occur when the trigger fires the starting gun.

Action Examples: Sending an email notification, generating a project management task, or modifying a database record.

Real-World Use Case: Your flow detects a new email with an attached invoice. It then retrieves invoice information and instantly changes your accounting system.

3. Connecting the Dots: Connections

Connections function like bridges, allowing your flow to interface with a wide range of external services and apps.

Connecting to: Office 365, SharePoint, Twitter, Salesforce, and pretty much any other supported service.

Imagine this scenario: You wish to send out an automatic tweet every time a new blog article is published on your website. Your flow uses a connection to Twitter to make it happen!

4. Flow of Information: Dynamic Content

Dynamic content is the heart of your flow. It is the information sent on by triggers and actions.

Consider: Extracted email subject, sender information, or file attributes such as size and name.

Put It into Action: When a new expenditure report arrives in your mailbox, your flow can extract the total amount from the email and automatically send it for approval.

5. Expressions.

They enable you to manipulate data dynamically, adding a layer of enchantment to flows.

Expression examples include combining text strings, computing dates, and extracting certain sections of text. Let's Get Specific: Use an expression to format a date pulled from a trigger into the exact format required by your calendar app.

6. Making decisions: Conditional logic.

Condition logic is analogous to your flow's "if-then" statements. They allow your flow to select options based on certain criteria.

Conditional examples include: "If the order exceeds $1000, notify the manager via email." Otherwise, continue with the standard processing." Likewise, "If a tweet mentions a specific product, reply with a discount code."

Real-life scenario: When a new client record is entered into your system, utilize condition logic to determine their location and allocate them to the right sales agent.

Would you like to see a video demonstration of some of the concepts? Check out the Youtube Channel: CDHQ

Wouldn't it be wonderful if upon your next login to Dynamics, you were promptly informed of significant events that occurred during your absence? Such as leads being assigned to you, opportunities closed by your team, or new cases opened.

Now, all of this is achievable through 'in-app notifications' for Dynamics 365.

Enable the feature within your model driven apps and users will see notifications when they log in, navigate pages or are on a page for more than a minute.

Enable the feature.

1. Navigate to the maker admin(https://make.powerapps.com/) and open the model-driven app you would like to enable this feature in and select the edit.
2. Select settings, Navigate to Features and enable 'In-app notifications'.

After refreshing your browser, you should see the notification bell in your header.

In this example I am going to create a notification when a new phone call record is created for case, and I am going to show the notification to the case owner. Obviously, you can use any trigger in Power Automate flow to create a notification.
We are going to create an automated cloud flow when creating the new flow. Click ‘+New Flow’ Make sure you name your flow, for my example I called the flow ‘In-App Notification on new call’.
For the trigger I’m going to use the ‘When a row is added, modified or deleted’. The change type is ‘added’ and the table name is ‘phone calls’. My scope is organization (I want this to run for everyone in the organization) and I am going to run this flow as the modifying user. That’s all you have to enter in the trigger step!

In the next step I am going to get case record.

In the next step we’re going to create the actual notification in data verse. Click on ‘+New Step’ and select ‘Add a new row’. For “Table name” select the ‘Notifications’ table.

The rest of this step is really about who the notification goes to and what we want to show in the notification.

In the “Title” field I am going to enter “New phone call has been added for your case!!!”. The title field will show in bold in the notification.

In the ‘Body‘ field I am going to enter “A new phone call has been added for your Case Number:” followed by the dynamic content in the case number field of the case that triggered the flow. The data in the ‘Body‘ field will show below the ‘Title‘ field in the notification.

The ‘Data‘ field in the step is a JSON structure to provide a more advanced control over the notification. links, and/or custom icons. However, those make for better notifications.

In the ‘Expiry (seconds)‘ field I will enter the number of seconds after which the notification will be deleted. I am going to set this for 20 minutes, which equals 1200 seconds.

The ‘Icon Type‘ field will allow you to choose an icon to be shown in the notification. There are a few icons you can use out of the box, and it looks like can use a custom icon as well. I haven’t figured out how to do that yet, so I am going to pick the out of the box “Info” icon.

The ‘Owner(Owners)‘ field represents who will see the notification,. Note that I entered /system users first and the dynamic content (Owner(value)) in parentheses.

Lastly you can set a priority and set the toast type to ‘Timed’. That’s all for the flow configuration! Make sure you save your flow and test it to make sure everything works as expected!

In Content, paste the following JSON. Replace the <entityLogicalName> with the entity name and <recordId> with the GUID of the specific record for which the link needs to be generated.
{

"actions":[

             {

"title": "Open Phone Call",

"data":{

"url": “?pagetype=entityrecord&etn=<entityligicalname>&id=<=recordId>",

"navigationTarget": "newWindow" }

              }

           ]               

}

I am going to add a phone call for a case now.

After the phone call created, a notification is received along with an action. Clicking on 'Open Phone Call' will open the popup case record.

After clicking the 'Open Phone call” action, the case record will be displayed in a new window.

Thank you..!

Out of the box, Power Apps supports Regular Expression (or RegEx) matching through in-built IsMatch, Match and MatchAll functions, however this is not natively supported within Power Automate.

If you have worked in the Power Automate space long enough, you have probably come across the request "can you turn this webpage into a pdf?"  In this quick step-by-step walkthrough, I will show you how to do this fast!

Summing up or getting an average an array should be easy, but sadly there isn't an out of the box way in Power Automate but there is a way 😎

Power Fx is a versatile language known for its simplicity and effectiveness in handling various data operations, including dates. In this blog post, we'll explore how to perform common date-related tasks using Power Fx Formulas in power automate desktop.

With everything moving to solutions I have been finding that sometimes the app user does not have permission to call the flow. This blog explains a workaround to fix it

This is a common question I have answered more than once here and it is time to revisit my accepted solution from August of 2023.  In this example, I will show you how you can reference a saved image you want to include as an embedded/inline image and include in a Send an email (V2) action from either OneDrive or SharePoint - the formats are slightly different.  Goes without saying, make sure the permissions on your image allow others to view (if applicable).

Some API's return a 302 redirect url, which Postman and other web clients automatically follow. Unfortunately its not that easy in Power Automate so here's how to fix it

📢𝗣𝗼𝘄𝗲𝗿 𝗙𝘅 𝗶𝗻 𝗣𝗼𝘄𝗲𝗿 𝗔𝘂𝘁𝗼𝗺𝗮𝘁𝗲 𝗗𝗲𝘀𝗸𝘁𝗼𝗽 now supports 𝗶𝗻𝘁𝗲𝗿𝗽𝗼𝗹𝗮𝘁𝗲𝗱 𝘀𝘁𝗿𝗶𝗻𝗴𝘀

𝗪𝗵𝗮𝘁 𝗶𝘀 𝗦𝘁𝗿𝗶𝗻𝗴 𝗜𝗻𝘁𝗲𝗿𝗽𝗼𝗹𝗮𝘁𝗶𝗼𝗻?
It is a powerful feature which allows you to inject variables, expressions directly into a standard string. It makes creating and formatting strings easier and more readable.
Used in programming languages. Also available in Power Apps and now in Power Automate Desktop.

𝗘𝘅𝗮𝗺𝗽𝗹𝗲:
🔷 Power Fx in PAD – 𝗪𝗶𝘁𝗵𝗼𝘂𝘁 String Interpolation
="Welcome, " & vFirstName & " " & vLastName & ", " & "this is a nice update in PAD Version 2.41"

🔷 Power Fx in PAD – 𝗪𝗶𝘁𝗵 String Interpolation
=$"Welcome, {vFirstName} {vLastName}, this is a nice update in PAD Version 2.41"


❗Key points to note and benefits:
🔹String interpolation strings begin with a $
🔹Use curly braces {} to evaluate and embed the variable or expression
🔹Both, normal text or interpolated strings can be used anywhere within that line of text
🔹No need of any ‘&’ operator, thus easy to read as well as write formatted strings.
🔹This is applicable only for Power Fx enabled desktop flows (in preview). The "=" sign in the beginning is the Power Fx notation.

Below screenshot shows an output in 𝗣𝗔𝗗 using Power Fx – 𝗪𝗶𝘁𝗵 String Interpolation

Check out my post for a sample on how Power Fx in PAD can be used.
https://lnkd.in/dd4cMTcH

This feature is released in the February update Version 2.41

https://lnkd.in/dcFCtD5N

Problem Statement:

Power Automate Desktop currently does not have an option to set categories to Outlook emails.

These are what categories in Outlook are. They can be default ones like Blue Category, Orange Category, or you can customize your own ones as shown below.

Power Automate Desktop Solution:

1. Launch Outlook and Configure the desired parameters for retrieving emails as per your specific criteria.

Here the email with the subject as "test email" in Inbox folder is configured.

2.  For the sake of this example only 1 email with the subject "test email" will be retrieved.

Hence, we are storing the unique EntryID of that email in a variable.

3. Here we are setting a variable with the desired Outlook categories

- Can pass single or as shown we are passing two categories at once.

- IMP: Make sure that you have the correct spelling of the category name as per the list of already configured categories in the outlook application. First screenshot of this write-up.

4.  Here we are simply passing the above two variables to a Vbscript which will do the rest ie; setting the category to the email having the specified EntryID.

VBScript Code:

Option Explicit

' Create Outlook Application object
Dim objOutlook
Set objOutlook = CreateObject("Outlook.Application")

' Get the message by its ID
Dim objNamespace, objMessage
Set objNamespace = objOutlook.GetNamespace("MAPI")
Set objMessage = objNamespace.GetItemFromID("%EntryID%")

' Check if the message is found
If Not objMessage Is Nothing Then
    ' Set the category
    objMessage.Categories = "%CategoriesToSet%"
    objMessage.Save ' Save changes
    
   ' MsgBox "Category set successfully."
Else
    'MsgBox "Message not found."
End If

' Clean up
Set objMessage = Nothing
Set objNamespace = Nothing
Set objOutlook = Nothing

5. The overall PAD flow would look as below.

*I have also attached the txt file of the entire flow which you need to copy-paste inside a blank Flow editor.

The flow is built in PAD version 2.41

6. Thats it. The email output after running the above PAD flow is as follows.

7. Attached .txt file of the flow to copy-paste into a blank PAD editor.

When you copy paste the code chances are that Power Automate Desktop adds some slash characters especially in the vbscript and you may see some errors. Single back slashes may become double back slashes. To fix, take the vbscript code snippet posted above and paste it directly into the "Run vbscript" action. 

User story: 

Create an access team whenever a new row is added to the Accounts table. Add the creator of the new row and their manager to the access team. Automate this process using power automate flow. 

What is an access team?

Access teams are a type of team that can be created in the Microsoft power platform to enable an extra level of security to your application. Access teams empower us to have a record level of security for our dataverse tables. Now, you might be wondering, when we already have some ways to achieve security in dataverse why use access teams?

Consider a scenario where an Azure Active Directory group has already been established for the purpose of restricting user access to a particular application. However, you do not want everyone in that AAD group to access all the records of that application. That is, you want some people to access only some records based on the ownership of the records. This is where the access group can help. With the help of power automate flows, you can automate to create access teams dynamically.

Everyone has their own particular style when making flows in Power Automate, and that is part of the beauty of being a developer. But development by its very nature is about sharing and learning from others (its why Stack Overflow is probably most visited developer site).

So after making far too many flows, I've pulled together what I think of as the best approach to Power Automate (and many other RPA tools), and it's called the 'Direct' methodology.

Adaptive Cards are self-contained user interface components that transcend platform boundaries. Crafted in JSON format, these snippets of UI can be seamlessly exchanged between applications.

Upon reaching a particular application, the JSON content is dynamically rendered into native UI elements, seamlessly blending with the app's aesthetic. This approach facilitates the creation and seamless integration of lightweight UI elements across diverse platforms and frameworks.

User Story:

We're preparing to implement a leave approval workflow in Teams utilizing adaptive cards. Employees will submit their leave requests, and line managers will receive notifications within Teams.

Step 1 – Design the Adaptive Card

Prior to establishing the flow, let's initiate the card design process using the designer tool to ensure readiness. Visit https://adaptivecards.io/designer/  to access the designer interface and adjust the 'host app' setting to Microsoft Teams – Light / Dark. Once the card example is updated, we can proceed with development.

Navigate to https://adaptivecards.io/designer and in Card Payload Editor upload below JSON.

{

    "type": "AdaptiveCard",

    "body": [

        {

            "type": "Container",

            "style": "emphasis",

            "items": [

                {

                    "type": "ColumnSet",

                    "columns": [

                        {

                            "type": "Column",

                            "items": [

                                {

                                    "type": "TextBlock",

                                    "size": "Large",

                                    "weight": "Bolder",

                                    "text": "**New Leave Request**"

                                }

                            ],

                            "width": "stretch"

                        },

                        {

                            "type": "Column",

                            "items": [

                                {

                                    "type": "Image",

                                    "url": "https://adaptivecards.io/content/pending.png",

                                    "altText": "Pending",

                                    "height": "30px"

                                }

                            ],

                            "width": "auto"

                        }

                    ]

                }

            ],

            "bleed": true

        },

        {

            "type": "Container",

            "items": [

                {

                    "type": "ColumnSet",

                    "columns": [

                        {

                            "type": "Column",

                            "items": [

                                {

                                    "type": "TextBlock",

                                    "size": "ExtraLarge",

                                    "text": "@{triggerOutputs()?['body/Title']}",

                                    "wrap": true

                                }

                            ],

                            "width": "stretch"

                        },

                        {

                            "type": "Column",

                            "items": [

                                {

                                    "type": "ActionSet",

                                    "actions": [

                                        {

                                            "type": "Action.OpenUrl",

                                            "title": "View Item",

                                            "url": "@{triggerOutputs()?['body/{Link}']}"

                                        }

                                    ]

                                }

                            ],

                            "width": "auto"

                        }

                    ]

                },

                {

                    "type": "FactSet",

                    "spacing": "Large",

                    "facts": [

                        {

                            "title": "Submitted By",

                            "value": "**@{triggerOutputs()?['body/Author/DisplayName']}** @{triggerOutputs()?['body/Author/Email']}"

                        },

                        {

                            "title": "Employee",

                            "value": "@{triggerOutputs()?['body/Title']}"

                        },

                        {

                            "title": "Start Date",

                            "value": "@{triggerOutputs()?['body/StateDate']}"

                        },

                        {

                            "title": "End Date",

                            "value": "@{triggerOutputs()?['body/EndDate']}"

                        }

                    ]

                }

            ]

        },

        {

            "type": "Container",

            "items": [

                {

                    "type": "ActionSet",

                    "actions": [

                        {

                            "type": "Action.Submit",

                            "title": "Approve",

                            "style": "positive",

                            "data": {

                                "id": "@{triggerOutputs()?['body/ID']}",

                                "action": "approve"

                            }

                        },

                        {

                            "type": "Action.ShowCard",

                            "title": "Reject",

                            "style": "destructive",

                            "card": {

                                "type": "AdaptiveCard",

                                "body": [

                                    {

                                        "type": "Input.Text",

                                        "id": "RejectCommentID",

                                        "placeholder": "Please specify an appropriate reason for rejection.",

                                        "isMultiline": true

                                    }

                                ],

                                "actions": [

                                    {

                                        "type": "Action.Submit",

                                        "title": "Send",

                                        "data": {

                                            "id": "@{triggerOutputs()?['body/ID']}",

                                            "action": "reject"

                                        }

                                    }

                                ],

                                "$schema": "http://adaptivecards.io/schemas/adaptive-card.json"

                            }

                        }

                    ]

                }

            ]

        }

    ],

    "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",

    "version": "1.2",

    "fallbackText": "This card requires Adaptive Cards v1.2 support to be rendered properly."

}

Step 2 – Building The Flow

• To create the Flow, Go to Power Automate -> Create -> Start from Blank -> Automated Flow.
• Give an appropriate name for the Flow and select the “When an item is created” trigger and click on Create button.

• Add “Post an Adaptive Card to Teams Channel and wait for response” action.

• Team: Select the Team in which you want to post the approval
• Channel: Select the Channel in which you want to post the approval
• Message: Copy the json given above and paste it in the message section and ensure the dynamic content is copied properly, or if you have built your own adaptive card then paste your json here and add any dynamic content as required.
• Update Message: Provide the update message, which will be shown after approver user has provided the decision using the card.
• Should update card: Select yes here.

• Add “Condition” action to check whether approver has approved or rejected the request, on left hand side of the condition copy.
• body(' Postadaptivecardandwaitforaresponse')['submitActionId'] expression (without quotes) and on right hand side provide “Approve” value or whatever your action value is defined in your adaptive card for the buttons.

• Under the “yes” branch to update the item and send message to the employee once leave request approval or rejected, do following.

• Finally, the navigate to SharePoint site and create a new leave request.

• Manger will receive message in teams chats please refer below screen short.

• Adaptive card wait for response.

• Once manager approve’ s the request employee will receive message in teams that his leave request is approved.

Complete Flow.

Thank you...!

In this post, we’ll work with a SharePoint List using The SharePoint Send HTTP Request action in Power Automate

we will see the most used methods, such as GET, POST, PATCH, and DELETE.

To access SharePoint resources using REST, construct a RESTful HTTP request by using the OData standard.

Method – Get

URL – https://{site_url}/_api/lists/getbytitle('{list_name}')/items

Accept – "application/json;odata=verbose"

• Log in to the flow portal with your Office 365 credentials.
• For this article, I have created a SharePoint List. Please find its schema below.

• Go to https://make.powerapps.com/, then click on "New Flow," choose "Automated cloud flow," provide a flow name, and select "when an item is created." Please consult the screenshot below for reference.

• Following Next, we must choose the site address and then select the list.

• Click on New Step and choose an operation pane, search for "Send an HTTP Request" under actions and select it.

In this window, please select the options as shown below.

• Site Address: Choose your SharePoint Site.
• Method: GET
• Uri: _api/web/lists/getbytitle('List Name')/items.
• Headers: As per business requirements.
• Body: JSON body as per business requirements.

• Execute a GET request and check for any issues.

Once GET request is executed, we need to do parse the response.

Take the result from preview step and generated JSON schema in Parse JSON.

The response body, which is in JSON format, we need to use apply to each action get a result from the previous step, and then we use Compose Action to get a specific result.

When we trigger the flow and see the result. Flow will get each item and display the Full Name, Email, and Employee Id as shown below.

Thank you..!

This is an FAQ and I wanted to share the flow so others can find it quickly and make it your own!  In this short walkthrough, we will email Microsoft Form attachments from a single question that allows more than one file upload and email them to someone.  At the end of the walkthrough, you will have the knowledge to do this yourself and most importantly, you will learn about the framework and actions you can use in other flows.  #neverstoplearning #sharingiscaring

I found this while working with a colleague and was faced with a sticky situation at work. I have this table in my database. However, I would like to send the data from the period date a day late. For example, I would like an email reporting Monday data on a Tuesday morning. So Friday reports Thursday data.

Now, here’s the problem. I would like to report Friday data, not Sunday data on Monday. 

How did we solve it? Let's find out