Power Platform

Dataverse Actions – Complete Guide (Model-Driven Apps) Dataverse Actions are a powerful feature in Microsoft Dataverse that allow you to execute custom business logic directly from model-driven apps, Power Automate, or external systems. Actions are typically used when you want to perform an operation that goes beyond simple create, update, or delete actions on a table. What are Dataverse Actions? A Dataverse Action represents a reusable business operation. It can accept input parameters, perform logic, and return output values. Unlike workflows or plugins that automatically trigger, actions are explicitly invoked by users or automation. In model-driven apps, actions are commonly exposed as command bar buttons, allowing users to trigger business logic manually from a form or grid. Types of Dataverse Actions Bound Actions – These actions are associated with a specific Dataverse table. They operate...

Power Automate Desktop – Variables and Operations In Power Automate Desktop, you can create different types of variables using the UI and assign values to them. For example: Text variable → value: sunil Number variable → value: 10 Boolean variable → value: True List 1 → add items: sunil, anil, zeshan, nithesh List 2 → add items: sunil, sachin, 20 Once variables are created, you can perform actions to modify and manage their values. Variable Operations Overview Number operations: Increase or decrease numeric values and round decimal numbers to a specific number of digits. Boolean variable: Holds True or False values for conditional checks. List operations: Perform advanced operations on lists of data. List Operations Explanation Sort List: Arranges items in alphabetical or numeric order. Shuffle List: Randomly changes the order of list items. Reverse List: Flips the list order from last to...

Power Automate Desktop Variables: Types and Usage In Power Automate Desktop (PAD), variables store data that flows through your automation. They can be referenced in actions using %VariableName% format. 1. Text Stores string values like names, messages, or file paths. Example: Set Variable: UserName = John Doe Display Message: Hello, %UserName% 2. Number Stores numeric values for calculations. Example: Set Variable: Age = 30 Display Message: You are %Age% years old 3. Boolean Stores True or False flags. Example: Set Variable: IsApproved = %true% Display Message: Approval status: %IsApproved% 4. List Stores multiple values in a collection. Access items by index. Example: Set Variable: EmployeeNames = [John, Mary, Steve] Display Message: First Employee: %EmployeeNames[0]% 5. Custom Object Stores key-value pairs. Access properties using dot notation. ...

When working with Microsoft Graph API inside Power Automate or Power Apps, many developers face this error: /me request is only valid with delegated authentication flow.   This happens because the HTTP connector with client credentials only works with application permissions , which do not provide a user context. If you need to call Graph API endpoints like /me , /me/messages , or /me/events , you must use delegated authentication . The best way to achieve this in Power Platform is by creating a Custom Connector with OAuth2 delegated flow . Step 1: Register an App in Azure AD  (Refer for more details: https://mspowerplatformtips.blogspot.com/2025/04/step-by-step-guide-power-automate.html ) Go to Azure Portal → Azure Active Directory → App registrations → New registration . Give your app a name (eg: Graph API Power Automate). Save the app and note down: Application (client) ID Directory (tenant) ID Step 2: Configure API Permissions In your register...

  Step 1: Install LocalDB Before proceeding, make sure LocalDB is installed on your computer. You can refer to the installation guide using this link . Step 2: Install SQL Server Management Studio (SSMS) Download and install SSMS by following this link . Step 3: Open SSMS Launch SQL Server Management Studio . You will see a window like the one shown below. Then, click on Connect . Step 4: Create a Database and Tables After connecting to the server, create a new database and the required tables as shown in the image below. To create a database: Right-click on Databases in the Object Explorer Select New Database Provide a name and click OK To create a table: Expand your newly created database Right-click on Tables Select New Table , then define your columns and data types Step 5: Install the On-Premises Data Gateway To connect your local database with cloud services like Power BI or Power Apps, you need to install the On-Premises Data Gateway . 👉 Click on this lin...

We are uploading files through Power Apps using the Attachment control. In the backend, a Power Automate flow uploads these files to OneDrive and assigns unique permissions . Since Power Automate does not have a built-in connector to directly assign unique permissions in OneDrive, we are handling this through the Microsoft Graph API (without using a custom connector). Step 1: Create a Blank Power Apps Application Open Power Apps Studio. Select New app > Start with a page design as shown below. Step 2 :  select Blank Canvas  Step 3: Add an Attachment Control In Power Apps, the Attachment control is not available directly from the standard controls list. To get the Attachment control: Add an Edit Form to your app. Connect the form to a SharePoint list . Once connected, the form will automatically include the Attachments field. You can then use this Attachment control to upload files. Step 4: Keep Only the Attachment Control Since we only need th...

Step 1: Open Power Automate, navigate to the Custom Connectors tab, and select Create from blank as shown in the image below. custom connector(click image for better resolution) Step 2: In the General tab, upload an icon (less than 1MB), add a description, select the correct scheme (in my case, HTTPS ), and provide the host name. For example, if your API URL is https://graph.microsoft.com/v1.0/users/{email} , the host name will be the highlighted part — graph.microsoft.com . Step 3: Go to the Security tab. Here, you need to select the authentication method. Choose OAuth 2.0 as the authentication type, as shown in the image below. Step 4: Select the Identity Provider as Azure Active Directory . Check the box Enable Service Principal Support . This option allows you to create a connection using a Client ID and Client Secret instead of using the user's own authentication. Next, provide the Client ID , Client Secret , Tenant ID , and other required details as shown in t...