Ssdt 2015 Saving as 2016 and Cannot Upload to Crm 2016

It was 1 of those unexpected errors that tin can bulldoze you lot crazy since they provide absolutely no details as to why they are happening.  Yet, I was not doing anything extraordinary – I was just trying to create an SSRS study for Dynamics 365(turned out that's an boggling task.. sometimes), information technology was xi PM on Fri dark (aye, I know.. who does information technology at 11 PM on Friday nighttime.. ), and I was constantly getting this mistake:

I was likewise getting it at 12 AM, and at 1 AM on Saturday, and, then, I chosen it a twenty-four hours and gave upwardly (just to go back to information technology on Sabbatum – see below)

The error went like this:

Fault Uploading Report
This report can't upload. This issue can occur when the Report Definition Linguistic communication (RDL) file is non valid. If yous contact support, please provide the technical details.
Activity ID: 47ebe340-68ed-4a4c-95b0-b5e1061c2b57

And, of grade, information technology had some details in the log file:

Unhandled Exception: Organisation.ServiceModel.FaultException`1[[Microsoft.Xrm.Sdk.OrganizationServiceFault, Microsoft.Xrm.Sdk, Version=8.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]]: An error occurred while trying to add the report to Microsoft Dynamics 365. Endeavour adding the report once again. If this problem persists, contact your system ambassador.Item:
<OrganizationServiceFault xmlns:i="http://www.w3.org/2001/XMLSchema-case" xmlns="http://schemas.microsoft.com/xrm/2011/Contracts">
<ActivityId>47ebe340-68ed-4a4c-95b0-b5e1061c2b57</ActivityId>
<ErrorCode>-2147188072</ErrorCode>
<ErrorDetails xmlns:d2p1="http://schemas.datacontract.org/2004/07/Arrangement.Collections.Generic" />
<Message>An mistake occurred while trying to add the written report to Microsoft Dynamics 365. Try adding the report again. If this problem persists, contact your system administrator.</Message>
<Timestamp>2017-06-18T01:11:45.2743564Z</Timestamp>
<ExceptionRetriable>faux</ExceptionRetriable>
<ExceptionSource i:nil="true" />
<InnerFault i:goose egg="true" />
<OriginalException i:zilch="truthful" />
<TraceText i:aught="true" />
</OrganizationServiceFault>

Unfortunately, those details were not peculiarly useful.

Did I mention I never created reports for Dynamics 365 on this particular laptop? So, before I started on Friday nighttime, I had installed the post-obit components:

• Visual Studio 2015 and Information Tools
• Report Authoring Extensions for Dynamics 365

That is supposed to be a supported configuration, co-ordinate to the download page:

https://www.microsoft.com/en-us/download/details.aspx?id=50375

And, yet, it was not working.

So, how practise you troubleshoot an consequence similar this? You can keep poking around, just at that place is a simple test:

• I've created a new written report using Dynamics report sorcerer
• And downloaded it
• And loaded it into the Visual Studio
• Did some pocket-size changes
• And tried to upload information technology back into Dynamics

Guess what – I got exactly the same error! Only that meant I was onto something, and the only possible explanation was that Visual Studio had updated the report in such a fashion that information technology became incompatible with Dynamics somehow.

What could be incompatible? It would likely be the format of that RDL file. The written report was working fine in the Visual Studio, though, so I spend nigh an hour looking at the schema, trying to get some clue.

And so I idea: is there really a style to target different versions of the SSRS server when building a report? That was actually the correct question, and there was an reply:

https://docs.microsoft.com/en-united states/sql/reporting-services/tools/deployment-and-version-support-in-sql-server-data-tools-ssrs

Did you happen to think it was the stop of it? Well, why would it exist.. I am writing a detective story hither:)

So, no, it was not the stop. I fabricated those changes, I configured the project to target 2008-2014 versions:

It was around 10 AM on Sat, btw..

And I tried uploading the report to Dynamics. The same stubborn error showed upwards once again!

I spent the following 30 minutes scratching my head – this was kind of beyond me. But you tin can't keep scratching your head forever when you need the report to be upwards and running.. then, why is it not making any difference. Was it the wrong pick? I was on the right track – that was my gut feeling at that fourth dimension. What did I miss? After a bit more scratching, I figured why don't I look at the rdl once again – may be I'd be able to spot the version number there? Sure enough, information technology was right there, right at the pinnacle of the file, and for some strange reason it was even so telling me the written report was targeting 2016 version:

Now this was strange..

What do we do when there is a question? Nosotros ask google. Here is what google answered:

https://stackoverflow.com/questions/36071175/can-i-command-the-version-of-new-ssdt-reports-in-visual-studio

God bless y'all, Google! And Rami A, whoever you are, who provided the final clue:

This is by design.

See https://connect.microsoft.com/SQLServer/Feedback/Details/2103422

Posted past Riccardo [MSFT] on 12/18/2015 at 5:07 PM
Past pattern, TargetServerVersion affects build output files, non source files. You deploy the build output files (which you can grab from the \bin\Debug or \bin\Release folder within your projection) rather than the source files.

And so there we go! If you lot ever run into this problem, do this:

• Alter the target server version of your report project (make it 2008, …, 2014)
• Build/Rebuild the project!!
• Do not upload the original rdl file to Dynamics – instead, use the one y'all'll observe in the "bin/debug" or "bin/release" folder

(and, probably, don't do those things in the new environs on a Friday night when you are supposed to be getting gear up for the weekend instead:) )

carsontherks.blogspot.com

Source: https://www.itaintboring.com/dynamics-crm/rdl-file-is-not-valid/

Share this post