MS Dynamics 365 CRM Custom Fetch Based Reports

Step 1 Check the Prerequisites

First thing first!! Do not forget to check the Prerequisites of the latest version of Report Authoring Extension and get the correct software versions installed in your system. For example, VS 2022 is not supported and hence you will fail to have the Custom Fetch based Reports option in the end.

So far, the lates version of VS that is supported is VS 2019. Make sure to have SSDT as a part of the installation as well.

Step 2 Install Reporting Services Project

In Visual Studio, if you don’t find Reporting Services Project, you may download from Manage Extensions (Online) and install.

Step 3 Install Report Authoring Extension

Download and Install Dynamics 365 version 9.0 Report Authoring Extension via the following link:

Step 4 Creating a Report

Once the installations are done, proceed with the following steps:

  1. Create a New Report Server Project via Visual Studio
  2. Right Click on Reports and Add New Report
  • Now you will be able to find the Microsoft Dynamics 365 Fetch option in Type.
  • Add Connections String separated by Semi Colon ; in the following manner:

CRM URL ; Organization Name


How to find the Organization name ?

In CRM, navigate to Settings>>Customization>> Developer Resources and copy the Unique Name to add in your connection string.

  • Add Credentials of your Trial CRM
  • Add a meaningful name to your Data Source
  • Proceed further to Login
  • After successfully logging in, you can add the relevant Fetch XML (by downloading from Advanced Find) to the Query String.
  • Complete the rest of steps necessary and Finish.
  • Use your innovation and aesthetic sense to design a beautiful report.
  • Preview your report in Visual Studio.
  • Deploy the rdl file to CRM.

Known issues

  1. Setup cannot continue because there is a pending restart required. Restart the computer and then try running Setup again.

Always check the path of Log file mentioned for any errors. For me, these were the errors:

“RunOnce contains Adobe Speed Launcher”

“RunOnce contains Delete Cached Update Binary

To resolve this issue, you need to delete the HKey twice, once with admin account and then with your logged in account. If you are the admin, then once is enough.

To fix this follow below steps. You can find same here in KB article…/2004114

Click Start, click Run and type regedit, and then click OK.

Locate the Registry Key listed in the Setup Log.  For example, the Registry Key isHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce.

Right click RunOnce, and then click Delete.

2. Some of the required components are missing. For more information, click Details.

On checking the details, it provides you with a link of Prerequisites. So check if you have all the appropriate things up and ready.

Resource not found for the segment ‘XXXX….’.

I was working on a Power Automate Flow to map the Case record GUID in Regarding of an Activity entity but it kept on giving me this error although there was no issues with the GUID or the record. Everything was fine. How did I fix this ?

Forward Slash then type the plural name of your entity and then within round brackets select the Unique Identifier :

Your flow should run successfully now!

Adding Buttons in the Ribbon – the Power Platform way!

So… back in old times we used to struggle with Ribbon Workbench for adding buttons in Dynamics 365 CRM. It was a nice way to do it but now we have an easier way out! Let’s welcome Power Fx Buttons!! 😀

  1. Add your desired entity (I will refer it as ‘Demo Entity’) in an App.
  2. Edit your App in Preview.

  1. Locate your entity (‘Demo Enity’) and click on the three dots to get the ‘Edit Command Bar (preview)’ option.
  1. Choose your desired selection and then click on Edit button. I am selecting Main Form.
  1. Click on New Command option. It will add a new button ‘NewCommand’. Rename it via the Label option in the right panel.
  1. You can add icon for your button from the same panel.
  2. Once you are done, click on Save and Publish button.
  3. For adding action to your button, select Run JavaScript from the Action Dropdown in the right panel.
  1. Define the Library and Function names , and your button is ready with the functionality.
  1. Here’s my nicely done button with icon on the Main Form.
  1. At times, I kept on getting a message Failed to delete component. Please delete the component from canvas studio. This was coming when I was changing the Action of the button. I simply reloaded the page and it was fine then. This might be a bug for the time being, as it is still in Preview mode. I hope it gets fixed before this is released officially.