Support

ReportBridge is a reporting infrastructure layer that migrates Microsoft SSRS paginated reports into Domo without rebuilding a single report. It pairs the Bold Report Viewer with Domo Everywhere embedding and PostgreSQL as the data backend, allowing organizations to fully decommission SQL Server, Windows Server, and SSRS.

ReportBridge is designed for enterprises with large SSRS report libraries (50 to 500+ RDL files) who cannot afford to rebuild every report in a dashboard tool. It is especially relevant for Domo customers, regulated industries where report format is dictated by regulatory bodies, and organizations migrating from SQL Server to PostgreSQL.

ReportBridge supports paginated reports defined in RDL and RDLC format — the standard file format used by Microsoft SQL Server Reporting Services. Report layouts, groupings, page breaks, headers, footers, sub-reports, matrix structures, and parameterization all transfer without modification.

SQL Server Reporting Services (SSRS) is Microsoft’s paginated reporting engine, used by an estimated 100,000 to 150,000 organizations worldwide. Microsoft has confirmed that SSRS will not receive new versions — SQL Server 2025 ships with Power BI Report Server instead — leaving organizations to migrate to Power BI, rebuild reports in another tool, or remain on aging infrastructure. ReportBridge provides a fourth option: preserve existing reports while exiting the Microsoft ecosystem entirely.

ReportBridge connects four layers into a single migration pipeline: (1) an Admin app for uploading and AI-converting RDL files, (2) a publish step that deploys converted files to Bold Report Viewer on AWS, (3) a render step where Bold Report Viewer reads the RDL natively and queries PostgreSQL, and (4) a Domo Everywhere iframe that embeds the rendered report inside a Domo card. All external operations route through an AWS Lambda API bridge.

Your original RDL files are uploaded to the Admin app, where an AI-assisted converter rewrites the embedded T-SQL queries to PostgreSQL syntax. The report layout, formatting, parameters, and visual structure remain untouched — only the SQL queries inside the RDL are modified. You can download the converted RDL files at any point.

No. Bold Report Viewer reads existing RDL / RDLC files natively, so no layouts are rebuilt. The only changes made to your report files are the SQL query conversions from T-SQL to PostgreSQL and the data source connection strings.

ReportBridge targets PostgreSQL as the data backend, using the Npgsql connector built into Bold Report Viewer. Your data must be migrated from SQL Server to PostgreSQL before reports can render. ReportBridge supports multiple PostgreSQL databases per deployment, with per-datasource mapping and alias resolution for multi-jurisdiction environments.

ReportBridge appears as two Domo apps: a Viewer app that end users interact with (featuring category navigation, search, and embedded paginated reports) and an Admin app for administrators to manage conversion, publishing, and access control. Both are installed from the Domo Appstore and run as native Domo cards.

No. End users access reports through their existing Domo login. The Viewer app authenticates through Domo Everywhere, and no separate credentials or accounts are required for report viewing.

Access control is enforced server-side using Domo groups. Each report in the catalog can be assigned to one or more Domo group IDs, and the Lambda API filters the report list so that each user sees only the reports their groups are authorized to view. There is no separate permission system to manage.

The Admin app sends each T-SQL query to Claude AI along with the relevant PostgreSQL schema context (table and column definitions). The AI rewrites the query to PostgreSQL syntax, handling patterns like ISNULL to COALESCE, TOP N to LIMIT N, GETDATE() to NOW(), DATEADD to interval arithmetic, and hundreds of others. Converted SQL is then validated via EXPLAIN against the live PostgreSQL database.

Roughly 80–90% of common T-SQL patterns convert without manual intervention. The system includes an automated test/fix loop that validates each converted query and feeds failures back to the AI for iterative correction, running up to five rounds per query. Reports with unusual or highly complex SQL may require manual review.

Bold Report Viewer supports a subset of VB.NET expressions commonly used in SSRS reports, including standard formatting, conditional visibility, and calculated fields. Complex custom assemblies or code blocks that reference external .NET libraries may require manual adjustment. The AI conversion focuses on SQL queries; report-level expressions are preserved as-is in the RDL file.

A typical ReportBridge deployment requires an EC2 instance (t3.medium) running Bold Report Viewer via Docker, a PostgreSQL database (RDS or EC2), an AWS Lambda function with API Gateway for the admin API bridge, and a domain with SSL certificate via Route 53 and ACM. Estimated infrastructure cost is approximately $52–$76 per month.

Yes. ReportBridge connects to any PostgreSQL database that is network-accessible from both the Lambda function (for SQL testing) and the Bold Report Viewer instance (for report rendering). If your PostgreSQL is in a private subnet, the Lambda must be placed in the same VPC with appropriate security group rules.

ReportBridge is designed for AWS cloud infrastructure. On-premises PostgreSQL databases can be used if they are network-accessible from AWS via VPN or Direct Connect. The Bold Report Viewer and Lambda components must run on AWS, though the PostgreSQL data source can reside anywhere with a reachable network path.

Bold Report Viewer is a report rendering engine from Syncfusion that natively reads and renders RDL / RDLC files on non-Microsoft infrastructure. It is the only commercially available engine that can render SSRS paginated reports without SQL Server or Windows Server, making it a critical component of the ReportBridge architecture.

Yes. Each customer must hold their own Bold Reports Enterprise license from Syncfusion. ReportBridge does not include or resell the Bold Reports license — it is procured directly from Syncfusion. Contact Syncfusion for current pricing and licensing terms.

ReportBridge has been validated with Bold Reports version 12.2.6 running in Docker. The deployment uses the syncfusion/boldreports Docker image with Docker Compose on Amazon Linux. Newer versions should be compatible but should be tested before production deployment.

All credentials (PostgreSQL passwords, Bold Reports admin credentials, API keys) are stored in a private Domo Config DataSet that is accessible only to the Admin app. The Viewer app reads a separate Viewer Config DataSet that contains no passwords, API keys, or database credentials. Lambda environment variables hold service-level credentials for Domo API and Bold Reports access.

All communication uses HTTPS/TLS throughout — between Domo and the Lambda API Gateway, between Lambda and PostgreSQL, and between Lambda and Bold Report Viewer. Domo DataSets are encrypted at rest by Domo. The Lambda API bridge uses parameterized queries, DDL/DML blocking, and read-only transactions to prevent SQL injection.

ReportBridge supports group-based access control where each report is filtered by Domo group membership. Row-level security within individual reports can be implemented through parameterized queries that filter data based on user context. The architecture supports per-jurisdiction database mapping for organizations that need data isolation across regions or business units.

ReportBridge is available through the Domo Appstore. The Bold Reports Viewer app (end-user report viewer) is free to install. The SSRS Migration Admin app (conversion pipeline, publishing, and management) is a paid or promotional offering. Contact ReportBridge for current pricing details.

Bold Reports is licensed separately by Syncfusion and is not included with ReportBridge. Customers must procure their own Bold Reports Enterprise license directly from Syncfusion. AWS infrastructure costs (EC2, Lambda, RDS) are estimated at $52–$76 per month for a standard single-jurisdiction deployment, paid directly to AWS.