CRIs are extensions to the Report Definition Language (RDL) that support custom objects that display data in a report.
CRIs include design-time and run-time components that are supplied by third-party software vendors.
Note Choosing to support custom report items on a report server is a decision made by the system administrator.
To view CRIs in a report, the CRI components must be installed on the report authoring client to preview a report and on the report server to view a published or uploaded report.
On first use, a report is either successfully upgraded or marked for backward compatibility.
Only the SQL Server 2016 Reporting Services (SSRS) report processor supports new features.
too many similar forums ) I've experienced the case where a newly added control doesn't get added to designer.cs, and been able to resolve it simply by cutting / pasting the control. The error list shows the warning "Generation of designer file failed: The method or operation is not implemented." 3. Investigating the possible differences between these files reveals no significant configuration differences, other than actual asp:xxx controls implemented on each page.The report could have existed on the report server before the upgrade, or the report could have been uploaded via Report Manager or published to the report server from Report Designer in SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, or SQL Server 2014 SQL Server Data Tools.The following table lists the upgrade action that is performed by the report server for specific types of CRIs in a report.When a user views a report or a report snapshot, or when the report server processes a subscription, the upgrading attempt occurs.The report definition is not replaced but continues to be stored on the report server in its original schema.
If a report cannot be upgraded, the report runs in backward-compatibility mode.