SSRS Compatibility
RDL Compatibility
Bold Reports® uses the same RDL architecture as SSRS, so most existing report definitions import and execute without redesign.
Supported Components
- Reports (RDL)
- Parameters
- Shared Datasets
- Shared Data Sources
- Tables
- Matrix Reports
- Charts
- Images
- Subreports
- Drill-down Reports
- Drill-through Reports
Requires Rework
The following are not carried over automatically by the migration process and typically require manual rework after migration:
- Custom assemblies and external code dependencies: the expression syntax referencing them is supported, but the assembly files themselves must be manually deployed to the Bold Reports® server — they aren't migrated automatically.
- SSRS subscriptions and delivery (email, file share) configurations: not migrated by the script; reconfigure these manually after migration.
SSRS Expression Support
Bold Reports® fully supports standard SSRS (VB.NET-based) expressions, so existing report expressions do not need to be rewritten after migration.
Examples:
=Sum(Fields!Sales.Value)
=IIF(Fields!Revenue.Value > 1000, "High", "Low")
=Globals!PageNumber
=User!UserID
Reference Documentation
For a deeper look at how Bold Reports® handles SSRS expressions, including the full list of supported functions, operators, and globals, see the following article:
What This Means for Your Migration
Because RDL and standard SSRS expressions are supported natively, most reports should require little or no rework during migration. Reports that use custom assemblies or external code dependencies are the exception. See Troubleshooting for guidance on expression errors.
SSRS subscription and scheduling configurations are not carried over by the migration script, so reconfigure delivery schedules manually in Bold Reports® after migrating the underlying reports.
Next: Now that you know which RDL components and expressions are supported, continue to Post-Migration Validation to confirm your migrated reports run as expected.