Report is not compliant after opening the RDLC in SQL Report Builder

I create a customized RDLC report. I export the file, open it in SQL 2016 Report Builder, and without any changes I save it. Then I try to import it and run the report. I get this error:

h8di7u4jiv58.png

Any thoughts?

Best Answer

Answers

  • binilabrahambinilabraham Member Posts: 45
    From what version you exported the report ? Did you compiled the report after importing it ?
    Software Developer,
    Archerpoint India Pvt. Ltd,Chennai.
  • KishormKishorm Member Posts: 921
    edited 2016-11-27
    Try using Report Builder from an earlier version of SQL, e.g. SQL Server 2012 / 2014 instead. I think it needs to be Report Builder version 3.
  • pabloquintanapabloquintana Member Posts: 20
    edited 2016-11-27
    Thank you both.

    @Kishorm I tried the 2014 version and it didn't open the files. I got a message complaining about the version from the beginning.

    'http://schemas.microsoft.com/sqlserver/reporting/2016/01/reportdefinition'

    @binilabraham it is NAV 2016 version. I am not sure which SQL server version is as we are using a cloud NAVonAzure version.

    I can't find anything about compiling after saving the .rdlc file. Can you point me to where I can do find more info about that?
  • KishormKishorm Member Posts: 921
    @pabloquintana What version is Report Builder in SQL Server 2014? (I haven't got it installed)

    If it's not Report Builder 3.0 then I think you'll need to use the Report Builder from SQL 2012 which is Report Builder 3.0
  • pabloquintanapabloquintana Member Posts: 20
    SQL Server 2014 Repor Builder v3.0
  • pabloquintanapabloquintana Member Posts: 20
    @Kishorm I opened a newly exported report. I will try again to make sure.
  • pabloquintanapabloquintana Member Posts: 20
    @Kishorm again you were right. I was exporting an already modified by the SQL Server 2016 Report Builder rdlc file. That is why the 2014 version was not able to open it.

    I started from scratch and Report Builder v3 is working fine now.
Sign In or Register to comment.