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:
- Create a New Report Server Project via Visual Studio
- 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.
- 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
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.