My dedicated website for all things Microsoft licensing (Power Platform, Dynamics 365, Copilot) has now been launched. Introducing: The Licensing Guide.
Continue reading The spirit of the licensing.guide at Jukka Niiranen blog.
My dedicated website for all things Microsoft licensing (Power Platform, Dynamics 365, Copilot) has now been launched. Introducing: The Licensing Guide.
In the Dynamics 365 and Power Apps ecosystem, we have several options for building applications, each one is for a specific type of requirement. Model-driven Apps works well when we need a structured UI with standard components, while we use Canvas Apps to create custom, mobile-friendly interfaces with a low-code approach. Recently, Microsoft introduced another application type called Code Apps, which offers a completely different way to build applications using pro code approach.
With the intr
In the Dynamics 365 and Power Apps ecosystem, we have several options for building applications, each one is for a specific type of requirement. Model-driven Apps works well when we need a structured UI with standard components, while we use Canvas Apps to create custom, mobile-friendly interfaces with a low-code approach. Recently, Microsoft introduced another application type called Code Apps, which offers a completely different way to build applications using pro code approach.
With the introduction of Power Apps Code Apps, things have changed. Code Apps let us build standalone single page applications using modern web frameworks. These are independent applications that cannot be integrated with Canvas Apps or Model-driven Apps.
The best part is that we get direct access to more than 1,500 standard and premium connectors through the Power Apps SDK. We do not have to write any authentication code, no OAuth flows, no custom APIs, no middleware. We just have to connect and use.
In this article, we’ll walk you through creating a Code App from scratch. We’ll build Personal Dashboard, a simple application that pulls assigned cases and leads from Dataverse and shows current logged in user details using the Office 365 Users and Dataverse connectors.
What Makes Code Apps Different?
We can build a UI of our own choice and connect to a wide range of data sources using more than 1,500 standard and premium connectors provided by the Power Platform. All connections are secure because the Power Apps SDK handles authentication, and each connector enforces user-level permissions. This means the app can only access data that the signed-in user is allowed to see, so there’s no need to write custom authentication code.
Code Apps provide a balanced approach with several key advantages:
A standalone application that runs directly within Power Platform
Full development with modern web frameworks such as React, Vue, or Angular, with support for your preferred libraries
Direct access to connectors through the Power Apps SDK without custom authentication code
Streamlined deployment through a single command to your environment
The connector integration is particularly valuable. Whether the need is to query Dataverse, access current user profile details, or use other services, the connector can be called directly. There’s no need to configure service principals, manage app registrations, or implement token management. The integration works seamlessly within the platform.
Prerequisites
Before getting started, we have to make sure the following prerequisites are in place:
Power Apps Premium license with Code Apps enabled environment
Visual Studio Code installed
Node.js LTS version
Power Platform Tools for VS Code extension
Step 1: Setting Up the Code App
Let’s create the app. Open VS Code, launch a PowerShell terminal, and run the following command:
For this application, we are using React as the framework and TypeScript as the variant. After that, navigate to the project folder and install the dependencies:
npm install
Install the node type definitions:
npm i –save-dev @types/node
After executing these commands, the project structure will appear as shown in the image below.
According to the official Microsoft documentation, the Power Apps SDK currently requires the port to be 3000 in the default configuration. To configure this, open vite.config.ts and replace the content with the following code:
Save the file and run the Code App locally by executing:
npm run dev
Browse to http://localhost:3000. If the application loads successfully, press Ctrl+C to stop the server.
Step 2: Initialize the Code App
First authenticate to Power Platform:
pac auth create
After that, sign in with the credentials and select the environment:
pac env select -env <environment-url>
Initialize the Code App:
pac code init –displayName “Personal Dashboard”
This will create a power.config.json file in the project as shown in the image below.
Now install the Power Apps SDK. This package provides APIs that allow the application to interact directly with Power Platform services and includes built-in logic to manage connections automatically as they are added or removed.
npm install –save-dev “@microsoft/power-apps
Update package.json to run both Vite and the Power Apps SDK server:
Open the URL provided by the Power SDK Server in the same browser profile as that of power platform tenant. Step 4: Adding Dataverse Connector
Now comes the part where we will add the data source to our application. In this step, we’ll use the Dataverse connector to fetch assigned cases and leads for the logged-in user.
Follow the instruction properly to create the connection, as shown in the
Once the connection is ready, we have to open the terminal. For Dataverse, we have to add the tables required for the application. For this example, we’ll add the Leads and Incident (Cases) tables using the following commands:
pac code add-data-source -a dataverse -t lead
pac code add-data-source -a dataverse -t incident
After running these commands, we can see that some files and folders are added to the project. Inside the generated folder, there are services and models folders. These contain the files for Leads, Incidents, and other tables, which can be used in the code. For example:
import { AccountsService } from './generated/services/AccountsService';
Import type { Accounts } from './generated/models/AccountsModel';
CRUD operations can be performed on Dataverse using the app. Before accessing any data, we have to initialize the Power Apps SDK to avoid errors. An async function or state check can ensure the SDK is ready before making API calls. For example:
useEffect(() => {
// Define a function of asynchronous type to properly initialize the Power Apps SDK to avoid any error during runtime
const init = async () => {
try {
await initialize(); // Wait for SDK initialization
setIsInitialized(true); // Mark the app as ready for data operations
} catch (err) {
setError('Failed to initialize Power Apps SDK'); // Handle initialization errors
setLoading(false); // Stop any loading indicators
}
};
init(); // Call the initialization function when the component mounts
}, []);
useEffect(() => {
If (!isInitialized) return;
// Place your data reading logic here
}, []);
Step 5: Adding Office 365 Users Connector
Similar to Dataverse, we need to create a connection for Office 365 Users by following the same steps. Once the connection is ready, we need to add it to the application. First, list all available connections to get the connection ID using command:
pac connection list
It will list all the connections available in the selected environment. We need to Copy the connection ID for Office 365 Users from the list, then add it to the project using:
pac code add-data-source -a “shared_office365users” -c “<connection-id>”
After running this command, the Office 365 Users connector will be available to use in the application, allowing access to user profiles, and other Office 365 user data.
Step 6: Building the UI
There are two ways to build a good UI. The first is the traditional coding approach where we write the complete code manually. The second is by using GitHub Copilot integrated in VS Code with the help of prompts.
Using GitHub Copilot:
We can generate the UI by writing a detailed prompt in GitHub Copilot. Here’s an example prompt:
Create a Personal Dashboard UI component in React with TypeScript that displays:
A header section showing the current logged-in user’s profile information (name, email, job title, and profile photo) fetched from Office 365 Users connector
Two main sections side by side:
– Left section: Display a list of assigned Cases (Incidents) from Dataverse
* Show case title, case number, priority, status, and created date
* Use card layout for each case
* Add loading state and error handling
– Right section: Display a list of assigned Leads from Dataverse
* Show lead name, company, topic, status, and created date
* Use card layout for each lead
* Add loading state and error handling
Use modern, clean UI design with:
– Responsive layout (works on desktop and mobile)
– Tailwind CSS for styling
– Professional color scheme (blues and grays)
– Proper spacing and typography
– Loading spinners while data is fetching
– Error messages if data fails to load
After providing this prompt to GitHub Copilot, it will generate the complete component code. We can then review the generated code, make any necessary adjustments, and integrate it into our application.
Step 7: Deploy Your Code App
Once the code is complete and the app is running locally, the next step is to deploy the application. For Code Apps, deployment is straightforward. First, build the application by running:
npm run build
After a successful build, execute the following command to push the application to Power Apps:
pac code push
This command will deploy the application to Power Apps. To verify the deployment, go to the Power Apps portal and open the Apps section. The newly deployed Code App will be visible in the list as shown in the image below.
To run the app, click the play button. On the first launch, the application will prompt for permission to access the connected data sources. After allowing the permissions, the application will use those connection references for all subsequent operations.
Conclusion
With Power Apps Code Apps, we can now build standalone applications. The real advantage here is the direct access to over 1,500 connectors through the Power Apps SDK. We can connect to Dataverse, Office 365 Users, and other services without writing any authentication code. The Power Apps SDK handles all the security, and each connector respects user level permissions automatically.
We also get complete freedom to design our own UI using any libraries we prefer. The deployment process is simple. Just run the build command and push it to Power Platform with a single command.
In this article, we built a Personal Dashboard that pulls data from Dataverse and Office 365 Users. The same approach works for any application that needs to connect with Power Platform services. The setup is straightforward, and once the project is initialized, adding new data sources is just a matter of running a few commands.
Code Apps provide a practical way to build custom applications within the Power Platform ecosystem while maintaining secure connections and proper access control.
Frequently Asked Questions (FAQs)
What are Power Apps Code Apps?
Power Apps Code Apps are a new application type in Microsoft Power Platform that allow developers to build standalone single-page applications using modern web frameworks such as React, Angular, or Vue. They provide direct access to Power Platform connectors through the Power Apps SDK without requiring custom authentication code.
How are Code Apps different from Canvas Apps and Model-Driven Apps?
Unlike Canvas Apps and Model-Driven Apps, Code Apps:
Are fully standalone applications
Use a pro-code development approach
Allow complete control over UI and application architecture
Cannot be embedded into Canvas or Model-Driven Apps
Use modern frontend frameworks instead of low-code designers
Do Power Apps Code Apps require authentication setup?
No. Authentication is handled automatically by the Power Apps SDK. Developers do not need to implement OAuth flows, manage tokens, or configure app registrations. All connectors enforce user-level permissions by default.
Can Power Apps Code Apps connect to Dataverse?
Yes. Power Apps Code Apps can connect directly to Dataverse using the Dataverse connector. Developers can perform CRUD operations on Dataverse tables, such as Leads and Incidents once the SDK is initialized.
How do Code Apps access Office 365 user information?
Code Apps use the Office 365 Users connector to retrieve profile details such as name, email, job title, and profile photo. The connector respects the signed-in user’s permissions automatically.
I recently released my first XRMToolBox plugin, “Dataverse Users, Security Roles, Teams and Teams Security Roles,” designed to help administrators, developers, and auditors easily explore detailed user access data within Microsoft Dataverse environments.
You can check the below articles in order for more details.
Dataverse Users, Security roles, Teams and Teams security roles (Overview)
Dataverse Users, Security roles, Teams and Teams security roles (Installation)
Datavers
I recently released my first XRMToolBox plugin, “Dataverse Users, Security Roles, Teams and Teams Security Roles,” designed to help administrators, developers, and auditors easily explore detailed user access data within Microsoft Dataverse environments.
You can check the below articles in order for more details.
In my previous articles, I introduced my plugin tool, “Dataverse Users, Security Roles, Teams, and Team Security Roles“ and explained how to install it using XrmToolBox. In this article, I’ll Walk you through how to use the tool effectively.
Follow the below steps.
Step 1: Open XrmToolBox and search for “Dataverse Users, Security roles, Teams and Teams security roles” in Tools tab.
Click on it.
Step 2: Click on Yes to connect to an organization.
Step 3: Select the
Step 1: Open XrmToolBox and search for “Dataverse Users, Security roles, Teams and Teams security roles” in Tools tab.
Click on it.
Step 2: Click on Yes to connect to an organization.
Step 3: Select the required connection and click on OK.
Tool has been opened successfully.
Step 4: Click on Load Data.
Tool will start retrieving all the System user details, Security roles (separated by semicolon ;), Teams (separated by semicolon and Team Security Roles (separated by semicolon ;).
Once, the Tool retrieves the data, you can see the data in the grid and also can see the number of users retrieved.
Step 5: Search for some text to filter the data.
As an example, I have entered the text “System Administrator“, and you can see the grid filtered with the entered text and can see the updated count as well.
If you want to sort, click on any column in the grid to sort ascending or descending.
As an example, I have clicked on Full Name to sort in Ascending order.
Step 6: Click on Export to export the data in CSV format.
Note: Data will be exported to the CSV format only on the filtered data, which you can see on this grid.
Step 7: Choose the required path and Provide the File name.
Click on Save.
Step 8: Once the data is exported successfully, you can see the Information message and the alert dialog with the Path, the file is downloaded.
Click on OK.
Step 9: Go to the Downloads folder and open the file to see the data.
Hope you liked my new XrmToolBox tool “Dataverse Users, Security roles, Teams and Teams security roles“.
Please like and share your valuable feedback on this article. Also, follow my blog to get my articles to your Inbox.
Click on the below image to navigate to my YouTube Channel.
Below are my earlier articles that you can have a look.
In my last article, I had explained about my new Plugin “Dataverse Users, Security roles, Teams and Teams security roles” overview and in this article, will explain about its installation.
Follow the below steps for installing this plugin in XrmToolBox.
Step 1: Click on the link to open XrmToolBox website.
Step 2: Click on the Download latest version.
Step 3: Click on Folder icon in Downloads.
Step 4: Right click on the folder and click on Extract All.
I have recently published my first XRMToolBox Plugin “Dataverse Users, Security roles, Teams and Teams security roles” related to Dataverse Security, which helps administrators, developers, and auditors retrieve and explore detailed user access information from Microsoft Dataverse environments.
You can check the below for the Overview, Key Features, Use Cases and Data Export of my Plugin.
Overview
This plugin provides a comprehensive view of Dataverse users and their access co
I have recently published my first XRMToolBox Plugin “Dataverse Users, Security roles, Teams and Teams security roles” related to Dataverse Security, which helps administrators, developers, and auditors retrieve and explore detailed user access information from Microsoft Dataverse environments.
You can check the below for the Overview, Key Features, Use Cases and Data Export of my Plugin.
Overview
This plugin provides a comprehensive view of Dataverse users and their access configurations, including:
User Details: UserId, ApplicationId, Full Name, Email, User Status, Business Unit, Azure AD Object ID etc.
User Security Roles (Separated by semicolon
User Teams (Separated by semicolon
Team Security Roles (Separated by semicolon
Key Features
Global Search: Use a single search box to find any text across all retrieved user fields
Column Sorting: Sort by any field for easier navigation and analysis
CSV Export: Export all data or filtered search results to a .csv file with a custom filename
Detailed Metadata: View additional fields like domain name, business unit ID, and application ID
Fast Performance: Optimized for large datasets with responsive UI
User-Friendly Interface: Intuitive layout with minimal setup required
Refresh Capability: Reload data without restarting the plugin with a single click
Offline Analysis: Exported data can be used for reporting, auditing, or compliance reviews
Use Cases
Security Audits: Identify users with elevated or missing roles
Compliance Reporting: Export user-role mappings for documentation
Team Management: Understand team memberships and inherited roles
Environment Cleanup: Detect inactive users or redundant access
Access Reviews: Analyze user metadata for governance and policy enforcement
Data Export
Click the Export button to download data as a .csv file
Choose your own filename
Export either full dataset or filtered results based on search
Hope you liked my new plugin in the XrmToolBox.
In the next article, will explain about how to install this plugin in the XrmToolBox.
Please like and share your valuable feedback on this article. Also, follow my blog to get my articles to your Inbox.
Click on the below image to navigate to my YouTube Channel.
Below are my earlier articles that you can have a look.
Overview
Microsoft Power Pages continues to evolve as a powerful platform for building secure, low-code, data-driven websites. One of its latest additions, the Summary Component, brings the power of AI summarization directly into portals.
The Summary Component allows developers and makers to automatically generate short, readable summaries from Dataverse data using the Power Pages Web API. This feature helps users quickly understand patterns, trends, and key details without navigating through i
Microsoft Power Pages continues to evolve as a powerful platform for building secure, low-code, data-driven websites. One of its latest additions, the Summary Component, brings the power of AI summarization directly into portals.
The Summary Component allows developers and makers to automatically generate short, readable summaries from Dataverse data using the Power Pages Web API. This feature helps users quickly understand patterns, trends, and key details without navigating through individual records.
This blog explains the implementation of the Summary Component for the Lead table in the Power Pages portal to summarize key fields such as Full Name, Creation Date, Annual Revenue, Subject, Company Name, Email, and Telephone Number.
Business Use Case
The goal of this implementation is to provide sales managers and team members with a quick overview of lead information directly from the portal without requiring them to open each record.
Traditionally, reviewing leads involves scanning through a detailed list of entries, which can be time-consuming. The new Summary Component solves this by generating a concise, AI-based paragraph summarizing all relevant leads.
Example: Instead of reading a table with multiple columns, the component can generate a statement like:
“In the last month, five new leads were created, including John Carter from Contoso Ltd. and Priya Mehta from Bluewave Technologies, both showing strong revenue potential.”
This not only saves time but also provides instant insight into the business pipeline.
Step-by-Step Implementation of Summary Component
The following steps outline the implementation of Power Pages Design Studio:
Step 1: Open Power Pages Design Studio
Open the Power Pages Design Studio and navigate to the page where the summary needs to appear.
Step 2: Add the Summary Component
In the selected section, click + More Options → Components → Connected to data → Summary.
Step 3: Configure the Component
In the configuration panel, fill in the details as follows:
Additional Instructions: “Provide a clear and concise summary highlighting the lead’s name, company, contact details, and the purpose or topic of the lead. Identify any patterns, urgency indicators, or follow-up requirements based on the creation date.”
Keep Summary Expanded: Enabled (This will keep the summary expandable by default when the user visits the portal)
This configuration connects the component to the Lead table via the Power Pages Web API and instructs it to summarize the specified fields.
Configuration Settings
Before the Summary Component can retrieve data, permissions and secure access must be configured through the portal.
Enable Web API for the Lead Table
Go to Power Pages Management → Site Settings → + New, and add the following key-value pairs:
Name: Webapi/lead/enabled
Value: true
Name: Webapi/lead/fields
Value: * (to allow access to all fields) or specify individual fields as fieldlogicalname1, fieldlogicalname2, …
This explicitly grants Web API access for the Lead table in the Power Pages portal.
Additionally, verify that the setting Summarization/Data/Enable is set to true.
If this setting does not exist, create a new record with that name and set its value to true.
2. Create Table Permissions
In Power Pages → Security → Table Permissions:
Create a new permission record with:
Name: All Leads or Lead Read Permission
Table: Lead
Access Type: Global access
Permission: Read
Assign this permission to the Authenticated Users web role.
Without this, data access via the Web API will fail with an error message:
“Something went wrong, please try again later.” error.
Working
Once the configuration is complete, publish the site and test the component.
The Summary Component will automatically connect to Dataverse, retrieve lead data, and generate a short summary paragraph that dynamically updates as new records are created or modified.
The output proved that the Web API connection and summarization logic were functioning correctly. The results dynamically update as new leads are added or existing records change in Dataverse.
Styling the Summary Component
The appearance of the Summary Component can be customized to align with the Power Pages portal theme. Styles such as borders, background colors, shadows, and other visual effects can be applied to ensure seamless integration with the overall site design.
FAQs
What is the Summary Component in Power Pages?
The Summary Component is an AI-powered feature in Microsoft Power Pages that uses natural language generation to summarize data from Dataverse tables, helping users understand key insights quickly.
Can I use the Summary Component for any Dataverse table?
Yes. It can be connected to any table with Web API access enabled. Just update the summarization API query and permissions accordingly.
Do I need to enable any specific settings before using the Summary Component?
Yes. Web API access must be enabled for the target table (e.g., Lead) and ensure the Summarization/Data/Enable site setting is set to true. Also, create the appropriate Table Permissions for the portal users.
Does the Summary Component automatically refresh when data changes in Dataverse?
Yes. Once configured, the summary updates dynamically whenever the underlying Dataverse records are modified or new data is added.
Can I style or customize the Summary Component UI?
Absolutely. The component’s appearance can be adjusted using custom CSS to align it with their Power Pages theme for a consistent visual experience.
Conclusion
The Summary Component in Power Pages is a game-changer for presenting Dataverse data in a meaningful, AI-driven format. By implementing it for the Lead table, sales teams gain quick, automated insights which resulted in saving time, improving decision-making, and enhancing user experience.
With minimal configuration enabling Web API, creating table permissions, and defining a summarization query the component delivers a seamless experience that transforms raw data into concise insights.
Workflows (also known as processes) in Dynamics 365 automate business logic such as approvals, field updates, or triggering other workflow actions. Sometimes, we need to check whether a workflow exists for a specific field before performing an action on a form.
For example, when updating sensitive fields like Credit Limit or Risk Category, you may want to warn users if workflows are already associated with these fields, since saving the record could trigger important automated processes.
In thi
Workflows (also known as processes) in Dynamics 365 automate business logic such as approvals, field updates, or triggering other workflow actions. Sometimes, we need to check whether a workflow exists for a specific field before performing an action on a form.
For example, when updating sensitive fields like Credit Limit or Risk Category, you may want to warn users if workflows are already associated with these fields, since saving the record could trigger important automated processes.
In this blog, we’ll explore:
Workflow categories and what they mean.
How to retrieve workflows related to a specific field.
A practical implementation where we check workflows before setting a Risk Category
Workflow Categories in Dynamics 365
In Dynamics 365, every workflow or process is assigned a Category value in the workflow table. For detailed insights into workflow properties, you can always check Microsoft’s official documentation for the latest updates. Below are the key category values:
Category Value
Workflow Type
0
Classic Workflow
1
Dialog
2
Business Rule
3
Action
4
Business Process Flow (BPF)
5
Modern Flow (Cloud Flow)
6
Desktop Flow
7
AI Flow
Use Case
Suppose you’re handling the Account entity in Dynamics 365.
When a user updates the Credit Limit, the system automatically sets the Risk Category (High, Medium, or Low).
But before setting this field, we want to check if any workflows (category = 5, i.e., Cloud Flows) are already linked with this Risk Category field.
If workflows exist, we show a confirmation pop-up to the user:
“There are workflows associated with this field. Saving may trigger them. Do you want to continue?”
This ensures users are aware of possible automated actions before proceeding.
Implementation in Power Apps (JavaScript on Form)
We’ll add a JavaScript function to the onChange event of the Credit Limit field.
Step 1: Retrieve Workflows from Dataverse
We query the workflow table using Web API and filter by:
Category = 5 (Cloud Flow)
clientdata containing our field (in this case, cre44_riskcategory)
Code:
// Helper function to check if workflows exist for a given field
async function checkAssociatedWorkflows(fieldLogicalName) {
try {
const query = "?$select=workflowid,name,clientdata" + "&$filter=category eq 5 and contains(clientdata, '" + fieldLogicalName.toLowerCase() + "')";
const results = await Xrm.WebApi.retrieveMultipleRecords("workflow", query);
return results.entities && results.entities.length > 0;
} catch (error) {
console.error("Error fetching workflows:", error.message);
return false; // fail safe → act like no workflows
}
}
Step 2: Handle Credit Limit Change
When the Credit Limit changes, we determine the Risk Category value and then check workflows.
Code:
// Function: Called on Credit Limit field OnChange
async function onCreditLimitChange(executionContext) {
try {
var formContext = executionContext.getFormContext();
var creditLimit = formContext.getAttribute("creditlimit").getValue();
if (creditLimit == null) return;
// Auto-set Risk Category based on Credit Limit
let riskCategoryValue = null; // OptionSet Values: 1=High, 2=Medium, 3=Low (example)
if (creditLimit > 100000) {
riskCategoryValue = 1; // High
} else if (creditLimit > 50000) {
riskCategoryValue = 2; // Medium
} else {
riskCategoryValue = 3; // Low
}
// Before setting High/Medium, check workflows
if (riskCategoryValue === 1 || riskCategoryValue === 2) {
const hasWorkflows = await checkAssociatedWorkflows("cre44_riskcategory");
if (hasWorkflows) {
Xrm.Navigation.openConfirmDialog(
{
title: "Workflows Detected",
text: "There are workflows associated with Risk Category. Setting it to High/Medium may trigger them. Do you want to continue?",
confirmButtonLabel: "Yes, Continue",
cancelButtonLabel: "No, Cancel"
}
).then(function (result) {
if (result.confirmed) {
// User confirmed → set field
formContext.getAttribute("cre44_riskcategory").setValue(riskCategoryValue);
} else {
// User cancelled → reset field
formContext.getAttribute("cre44_riskcategory").setValue(null);
}
});
} else {
// No workflows → set directly
formContext.getAttribute("cre44_riskcategory").setValue(riskCategoryValue);
}
} else {
// Low risk → set directly
formContext.getAttribute("cre44_riskcategory").setValue(riskCategoryValue);
}
} catch (error) {
Xrm.Navigation.openAlertDialog({
title: "Error",
text: "A failure occurred in Web API.\nDetails: " + error.message
});
}
}
Execution in Account Form
1. Add the provided JavaScript web resource within your Dynamics 365 solution.
2. On the Account form, bind the onCreditLimitChange function to the Credit Limit field’s OnChange event.
3. Publish and test:
If workflows exist for Risk Category (and it’s set to High/Medium), you’ll get a confirmation popup, and if no workflows exist, the field is updated directly.
Summary
Workflows in Dynamics 365 are categorized by type (Classic, Dialog, Action, BPF, Cloud Flow).
Retrieve workflows from the workflow table by executing Web API queries.
In our example, we checked for Cloud Flows (category 5) linked to the Risk Category field before updating it.
This approach adds a safety layer, ensuring users are aware of automation that might get triggered.
This method is very useful when dealing with sensitive fields like Credit Limit, Risk Category, or Approval fields in Dynamics 365.
Conclusion
Identifying workflows linked to specific fields in Dynamics 365 helps avoid unexpected automation. It ensures better control while updating sensitive fields like Credit Limit or Risk Category. This improves system reliability and reduces troubleshooting efforts. Overall, it empowers admins to manage workflows with confidence.
Show/ hide views in Dynamics 365 based on security roles
The post Role Based views in DataVerse/ Dynamics 365 appeared first on Debajit's Power Apps & Dynamics 365 Blog.
This is a quite common requirement from the business to send automated emails on some Dataverse record create/ update / delete using Microsoft No Code/ Low Code platform.
In this article, will explain about the below requirement step by step using Power Automate.
Requirement: Send an Email to Customer (Contact) when the contact record is created.
Follow the below steps.
Pre-requisites:
Configure donotreply email using Shared mailboxes in Dynamics 365 CE
Understanding
This is a quite common requirement from the business to send automated emails on some Dataverse record create/ update / delete using Microsoft No Code/ Low Code platform.
In this article, will explain about the below requirement step by step using Power Automate.
Requirement: Send an Email to Customer (Contact) when the contact record is created.
Step 15: Give the QueueId in Activity Party participationmask 1.
Place the cursor in the Contacts braces and Click on Insert dynamic content.
Step 16: Search for Contact and Click on Contact (Unique identifier of the contact).
After insertion,
Step 17: Enter the below text in the Description field. Place the cursor after Dear . Click on Insert Dynamic content.
Dear ,
Welcome to Arun Potti Corp! We’re excited to have you with us. Stay tuned for updates, insights, and exclusive content. Feel free to reach out with any questions—we’re happy to connect!
Best regards, Administrator
Step 18: Search for Full Name and Click on Full Name.
After insertion,
Step 19: Place the cursor on the Due Date and Click on Insert Expression.
Step 20: Enter the below expression and click on Add.
utcNow()
Step 21: Give the below text and place the cursor on Regarding (Contacts) in the braces. Click on Insert Dynamic content.
/contacts()
Step 22: Search for Contact and Click on Contact (Unique identifier of the contact).
After update,
Step 23: Give the below Subject.
Welcome to Arun Potti Corp!
Step 24: Click on Add a new row and update the Name to Create contact welcome email.
After update,
Step 25: Click on Save and after Save click on + icon to add new action.
Step 26: Search for Perform a bound action and click on it (Microsoft Dataverse -> Perform a bound action).
Step 27: Select the Table name as Email Messages. Choose the Action Name as SendEmail. Place the cursor in the Row IDfield. Click on Insert Dynamic content.
Step 28: Search for Email Message and Click on Email Message (Action: Create contact welcome email).
After insertion,
Step 29: Select the Item/IssueSend to Yes.
Step 30: Update the Action to Perform a bound action – Send Email and Click on Save.
Step 31: Once Power Automate is saved. Go to any Model-driven App. Create a new Contact record to test the welcome email flow.
Note: Make sure to provide the Email address when creating the Contact.
You will get the email once the flow executed successfully.
Hope you have successfully sent the email after creating the contact using Power Automate by following all the above steps.
Please like and share your valuable feedback on this article. Also, follow my blog to get my articles to your Inbox.
Click on the below image to navigate to my YouTube Channel.
Below are my earlier articles that you can have a look.
Login
