- #Report authoring extension crm 2016 download how to#
- #Report authoring extension crm 2016 download movie#
You don't have to create Fetch XML from scratch.
#Report authoring extension crm 2016 download how to#
In that way I can also show you how to get Fetch XML from advanced find.
#Report authoring extension crm 2016 download movie#
Based on the Genre selection, the movie records belonging to that Genre will be shown.įor my blog I will simply download the Fetch XML created automatically by advanced find. It cannot be a TSQL using filtered views.Īs I mentioned above, I will have Genre records as a pick list report parameter. Since it is a Fetch XML based report, the query to get genres will be a Fetch XML. Click OK and a data source is created by the name "SQLConnection".ġ1) I will create a dataset for Genres. I have to specify the CRM Organization for which this report will be running. In the connection string, I cannot specify a direct connection to my SQL Server CRM database. In the embedded connection, select the type as "Microsoft Dynamics CRM Fetch".
I have named my data source as "SQLConnection". Give a name and define a connection to the SQL Server CRM database. This will open a "Data Source Properties" window.ġ0) Shown below is the "Data Source Properties" window. This is a connection to my SQL Server CRM database.Ĭlick on Data Sources > Add Data Source. This option will create an empty report file with the extension of rdl (report definition language).Ĩ) In the screenshot below, you can see the report "Movies by Genre.rdl" has been created.ĩ) In the report, I will add a data source. I will give this report a name "Movies by Genre". You deploy the build output files (which you can grab from the \bin\Debug or \bin\Release folder within your project) rather than the source files.7) In the "Add New Item" window, select a file of type Report. God bless you, Google! And Rami A, whoever you are, who provided the final clue:īy design, TargetServerVersion affects build output files, not source files. What do we do when there is a question? We ask google. What did I miss? After a bit more scratching, I figured why don’t I look at the rdl again – may be I’d be able to spot the version number there? Sure enough, it was right there, right at the top of the file, and for some strange reason it was still telling me the report was targeting 2016 version:
Was it the wrong option? I was on the right track – that was my gut feeling at that time. But you can’t keep scratching your head forever when you need the report to be up and running. I spent the following 30 minutes scratching my head – this was kind of beyond me. I made those changes, I configured the project to target 2008-2014 versions:Īnd I tried uploading the report to Dynamics. The report was working fine in the Visual Studio, though, so I spend about an hour looking at the schema, trying to get some clue.Īnd then I thought: is there actually a way to target different versions of the SSRS server when building a report? That was actually the right question, and there was an answer:ĭid you happen to think it was the end of it? Well, why would it be. What could be incompatible? It would likely be the format of that RDL file. Guess what – I got exactly the same error! But that meant I was onto something, and the only possible explanation was that Visual Studio had updated the report in such a way that it became incompatible with Dynamics somehow. And tried to upload it back into Dynamics.I’ve created a new report using Dynamics report wizard.So, how do you troubleshoot an issue like this? You can keep poking around, but there is a simple test: That is supposed to be a supported configuration, according to the download page:
It was one of those unexpected errors that can drive you crazy since they provide absolutely no details as to why they are happening.