
While I love Power BI, my client will neither permit its use nor purchase licenses to author reports in the system they did choose to the Dynamics team. So, I attempted to fall back onto SSRS in order to shame the people making these decisions.
To my shame, on a brand new VM with a licensed copy of VS2019 with SSDT package, I cannot get any of the Fetch authoring extensions to install nor to tell me what component is actually missing...and don't tell me I need to get a license for VS2015 (because I tried installing VS2015 Desktop Express and it still fails.)
In the dark ages of Dynamics SDKs, we used to modify the config packages to support the modern IDEs....what do I need to do in the scenario I've described (brand new VM with VS2019 and SSDT package)?
What I'd like to avoid is 1) letting the non-reporting continue (because output drives input in a Dynamics system, and if I don't have a say in the output, I'll never capture the right input) and 2) having to create my own HTML module to create the kinds of reports I want along with an export to Excel button. (Actually, I have done option 2 already for ad hoc reporting where I've trained my business users to submit FetchXML....but I'd prefer to show them something more elegant for the monthly reports they deliver to their CFO and CEO.)
Thanks,
Mike
On a scale of 0 to 10, MS cranks it up to 11 again for messages that politely encourage you to buy from their competition =/
Hey Mike,
Please try to use the latest available Report Authoring Extension (with SQL Server Data Tools support) for v9 ::
www.microsoft.com/.../details.aspx
One of the community articles which talk about setting up Developer Toolkit for VS2019 with Core Assemblies
community.dynamics.com/.../setting-up-developer-toolkit-for-vs2019-with-core-assemblies-9-0
https://superuser.com/questions/1495556/dynamics-365-developer-toolkit-for-vs-2019
Please mark my answer if this helps.
Thanks,
Saurabh