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!!!