Microsoft Dataverse is a powerful data platform that supports secure and scalable data storage for business applications. However, raw data imported into Dataverse often needs transformation—cleaning, reshaping, filtering, or merging—to make it useful and reliable for apps and analytics.  In this blog, we’ll show you how to apply transformations to data before or after it reaches Dataverse using tools like Power Query, Dataflows, and business rules—ensuring you always work with clean, structured, and actionable data.  What is Data Transformation in Dataverse?  Why Data Transformation Matters Data transformation refers to modifying data’s structure, content, or format before or after it’s stored in Dataverse. This includes:  Step-by-Step Guide: Connecting a Database to Dataverse  Step 1: Open the Power Apps and select the proper Environment  Step 2: Open Dataflow in Power Apps and create a new Dataflow  Step 3: Connect to the Database using SQL Server Database.  Step 4: Add the required credentials to make the connection between the database and Dataverse.  Step 5: Add the transformation in the Dataverse  Step 6: Add proper mapping of the column and find the unique ID of the table   Step 7: Set the schedule refresh and publish the Dataflow.  Step 8: Once Dataflow is published, we can see the table in the Power apps  To conclude, transforming data in Dataverse is key to building reliable and high-performing applications. Whether using Power Query, calculated columns, or Power Automate, you can ensure your data is clean, structured, and actionable.  We hope you found this blog useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfonts.com. Ready to improve your Dataverse data quality? Start with a simple dataflow or calculated column today, and empower your business applications with better, transformed data.

Modern applications demand seamless, real-time data access. Microsoft Dataverse—the data backbone of the Power Platform—makes it easier to build and scale low-code apps, but often your enterprise data resides in legacy databases.  Connecting a database to Dataverse enables automation, reporting, and app-building capabilities using the Power Platform’s ecosystem. In this blog, we’ll walk you through how to connect a traditional SQL database (Azure SQL or On-Premises) to Microsoft Dataverse.  What is Dataverse?  Dataverse is Microsoft’s cloud-based data platform, designed to securely store and manage data used by business applications. It’s highly integrated with Power Apps, Power Automate, and Dynamics 365.  Key Features:  Why Connect Your Database to Dataverse?  Step-by-Step Guide: Connecting a Database to Dataverse  Step 1: Open the Power Apps and select the proper Environment  Step 2: Open Dataflow in Power Apps and create a new Dataflow  Step 3: Connect to the Database using SQL Server Database.  Step 4: Add the required credentials to make the connection between the database and Dataverse.  Step 5: Add proper mapping of the column and find the unique ID of the table   Step 6: Set the schedule refresh and publish the Dataflow.  Step 7: Once Dataflow is published, we can see the table in the Power apps  To conclude, connecting your database to Dataverse amplifies the power of your data, enabling app development, automation, and reporting within a unified ecosystem. Whether you need real-time access or periodic data sync, Microsoft offers flexible and secure methods to integrate databases with Dataverse.  Start exploring virtual tables or dataflows today to bridge the gap between your existing databases and the Power Platform. Want to learn more? Check out our related guides on Dataverse best practices and virtual table optimization. We hope you found this blog useful. If you would like to discuss anything further, please reach out to us at transform@cloudfonts.com.

Low-code development has revolutionized the way businesses build software applications. By providing a visual, drag-and-drop interface, low-code platforms enable developers to quickly create complex applications without writing much code. However, even with the power of low-code platforms, there may be times when you need to extend their capabilities to meet specific business requirements. This is where low-code plugins come into play. Low-code plugins are small pieces of software that can be added to a low-code platform to extend its functionality. In this blog post, we will discuss the benefits of using low-code plugins, the steps involved in creating them, and some tips for successful development. Benefits of Using Low-Code Plugins Low-code plugins offer a number of benefits for businesses, including: Steps in Creating a Low-Code Plugin The process of creating a low-code plugin typically involves the following steps: Tips for Successful Low-Code Plugin Development Here are some tips for developing successful low-code plugins: Example Use Cases Low-code plugins can be used to solve a variety of business problems. Here are some examples: Conclusion Low-code plugins offer a powerful way to extend the capabilities of low-code platforms and create custom solutions that meet specific business needs. By following the steps outlined in this blog post and incorporating the tips for successful development, you can effectively leverage low-code plugins to drive innovation and achieve your business objectives. Later we will see working of the Low-Code Plugin in Dynamics 365 CRM with an example. We hope you found this blog useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfonts.com.

Introduction Document management is a critical aspect of any organization using Dynamics 365 CRM, and finding a simple, scalable solution can often be a challenge.  In this blog, I’ll show you how PowerApps Custom Pages can transform your document handling experience. By leveraging model-driven capabilities, I’ve built a solution from scratch that allows you to handle multiple document templates at once without the complexity and clutter of traditional methods. Using Custom Pages, you can generate and organize documents across different entities directly within the Dynamics 365 environment, making it easy to scale your solution for any table or scenario. Let’s take a closer look at how Custom Pages can streamline and simplify document management for your organization. The Use-Case: Document Management Application Key Components of the Solution which I have chosen for this use-case and blog Step-by-Step Process Step 1: Create the Custom Page (refer to my previous blog if needed) Create a solution, create custom Page and then embed it into Model-Driven App. I’ve made a sample example below: Step 2: How to retrieve parameters when App is opened. For the App’s ‘OnStart’ property, enter the following code Step 3: Trigger Document Generation App (I have used a ribbon button to trigger using JS) You will need to write a JavaScript in order to trigger and display the Custom Page. Where to find the app name, you will find in the solution. My example is below Step 3: Trigger Document Generation Page Once the document is created, you can close the Page using X button. As per JS code, our code will navigate to Document Tab. Ensure the name of Document Tab is correct. Step 4: Automation to SharePoint Use PowerApps Connector and add your input parameters to it. In the Custom Page, do insert the newly created Power Automate flow and pass the input values respectively Also, once the flow is completed, you can send a response back to Custom Page using same connector but of different action ‘Respond to PowerApp or Flow’. Conclusion Conclusion This Custom Page use-case demonstrates how a thoughtfully designed solution can enhance productivity and user experience in Dynamics 365. By streamlining document creation and navigation, it reduces friction in day-to-day operations, empowering teams to focus on higher-value tasks. Whether you’re a technical developer or a functional consultant, this approach provides actionable insights for building powerful and efficient solutions. References We hope you found this blog useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfonts.com. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut elit tellus, luctus nec ullamcorper mattis, pulvinar dapibus leo.

What Makes Custom Pages Unique? Key Differences Between Custom Pages and Canvas Apps Benefits of Using Custom Pages in D365 Conclusion In conclusion, Custom Pages stand out as a powerful tool for enhancing the functionality and user experience within the D365 ecosystem. By offering seamless integration with Model-Driven Apps, advanced design capabilities, and tailored interactions, Custom Pages provide users with a dynamic, responsive interface that feels native to the D365 environment. While Canvas Apps offer broader cross-platform flexibility, Custom Pages excel in scenarios requiring deep integration and advanced Model-Driven functionalities. Whether you’re looking to improve user engagement or create personalized, context-sensitive workflows, Custom Pages offer a unique advantage, making them an essential tool for any D365 implementation. We hope you found this blog useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfonts.com. Reference Links PowerApps Custom Page: Microsoft Documentation – Custom Page

Hi All, I’m going to show a useful feature that you can leverage to view and create instant Power BI visuals that is generated automatically based on the current view. Documentation Link Just an example: How it looks Steps to achieve this: Step 1: You need to enable this feature in Model-Driven App itself Edit Model-Driven App -> Settings -> Features -> ‘Enable Power BI quick report visualization on a table‘. Save and publish the settings Note: You also need ‘TDS endpoint‘ enabled in the environment feature settings Step 2: Refresh your browser and navigate to any table records view ( I took cases in the example) Step 3: Click the ‘Visualize this view‘ button on the command bar Note: You need to add the necessary columns in the current view if you want to show those columns in Power BI Reports Step 4: You can now see the Report generated automatically within a few mins. You can save these Reports if all necessary information is displayed here. Hope this helped you get faster Business Insights with auto-generated Power BI visuals.

Hi All, Have you ever wondered how to use Dataverse In-App notification that can be helpful in many scenarios, I’ll give an overview of the usage with a use-case. Documentation Link Business Insights in Real-Time – Documentation This is the In-App Notification Let’s see how to create such an In-App notification Step 1: In order to use this In-App notification, we need to enable it. -> Go to Editor of Model-Drivel App -> Click on Settings -> Click on ‘Features’ -> Enable ‘In-App Notification’ Note: This In-App notification creates records in Dataverse, therefore the storage will be consumed. There’s also a time-based auto-deletion that can be configured by Admin. Step 2: Save & Publish your Model-Driven App. You will see a Bell Icon on the top-right of the App. Step 3: Now, we will create the notification. There are 3 ways to create the notification, Using JavaScript -> will be using in this example Using C# Plugins (Dataverse SDK) Using HTTP Request (Web API) Step 4: As example, I will be sending a Notification to me but you can configure it to send to anyone in the organization. Note: You must have the necessary permissions to do so, Admin can configure these privileges by customizing Security Roles for the ‘app notification‘ table Refer what type of format you want to display from the documentation link provided above Step 5: I’ve created a Web-Resource that triggers when I manually close the case, So when I close a case, here’s the output. Note: You can automate these and send to anyone.Some examples are:1. Automatic send Notification of new case created to assigned person.2. Automatic notification to the Team whenever a critical ticket is raised.3. Apart from these, you can have notification whenever a Business critical flow has been failed. Some of the best ways to use is with having rich user experience with Icons and formatting options that are available to use.Icons, font styling and mentioning anyone That’s how we can achieve In-App notifications. Hope this helped you!

In case it’s your first time creating a Cloud Flow using Dataverse connector and dealing with Primary Key of the Activity Type of entity, here’s a quick tip to keep in mind. Normal Entity As a creator for Flow, let’s say you have listed Records of an entity called as Accounts (out-of-the-box), you’ll notice that the name of the entity Activity Entity Now, if you try to search for the Name of the Activity entity, it won’t appear as it does for other entities, instead just search “Unique” and you’ll find an entry for Unique identifier of the activity entity – Name of my Activity entity is ‘Snapshot’, but it doesn’t show up when I search Snapshot. So instead, just search “Unique” or “Identifier” On the contrary, out-of-the-box entities have their own names named as Primary Keys Hope this is useful!

In this blog, we will learn how to store the Customer Voice survey response to the custom entity as OOB entities which holds that response data is complex and data is stored in multiple related entities. Step 1: Create a Customer Voice Project and Survey Log in to the Customer Voice Portal and Create a new Project. Select a Blank Template and click on Next. After creating a survey you need to select the Environment location in which Customer Voice Data will get stored. To select the location click on See all environment. Select the Environment location and complete the configuration of the Project. Step 2: Add the Survey Form Fields. Now, we will add the fields that need to be filled by the target audience or based on requirements. After creating your Survey form, you can click on the Preview to view in Desktop and Mobile Mode. To share the form, click on the “Send” tab. There are three options by which you can share the survey form — Scan the QR Code, Embed the Form in Website or App, and share using a short link. I will copy the short link and use it to fill the survey form. You can also create Cloud Flow to automate the survey sending process. Comment down below if you want a blog on the same. Let’s see it in action, I have submitted one response in Survey that we have created. Customer Voice Survey CSD Entity: During the configuration of the Customer Voice Project, we have selected the environment location. In that environment, there are some OOB Entities that have been created to store the Customer Voice Survey Data in CDS / Dataverse. We will Open the CRM Environment and we will Advance Find for the “Customer Voice Survey”. After clicking on the result, you will see the survey that we have created from the Customer Voice portal is also visible in Dynamics 365 CRM as shown below screenshot. Open the Customer Voice survey record. Go to Related and select the “Customer Voice survey responses”. You will see the response that we have submitted after the creation of the Survey Form. Open the Customer Voice survey responses record. To see the responses to each question submitted by the Audience, open the Related “Customer Voice survey question responses”. Open any Customer Voice survey question responses record. You have two fields Question — Lookup to Customer Voice Survey Questions Response — String value of responses submitted by the audience. Link to Documentation:Entity Reference for Dynamics 365 Customer Voice Step 3: Create a Custom Entity and Cloud Flow. I have created a Custom Survey response entity that has the same fields to store the response when any audience submits the response. Step 4: Create Cloud Flow to store the responses to Custom Entity. Create a flow and the trigger will be “When a row is added, modified or deleted” Dataverse connector. Configure the Triggering Connect as shown below screenshot: Now, we will list all the records of responses. To do so we need to use the “List rows” Dataverse connector and configure it as mentioned in the screenshot. We will declare the Variable to store all the question responses. These variables will be used to create the new Custom Survey Response. We will add a switch case that will match the Questions and store the responses to the respective Flow variable. After adding all the switch cases, we will create a record in CDS / Dataverse using the “Add a new row” Dataverse connector. Save the Cloud flow and test it. Cloud Flow in action Hope this helps!!!