Under 1 hour

Quick-Start Guide

Get your first SSRS paginated report rendering in Domo in under an hour.

Prerequisites

Domo instance with Pro Code app publishing capability and a Domo OAuth client (Client ID + Secret with data and user scopes)
AWS account with permissions to create Lambda functions, API Gateway endpoints, and EC2 instances (or ECS Fargate)
PostgreSQL database containing your migrated SQL Server data, accessible from both AWS Lambda and your Bold Report Viewer instance
Bold Report Viewer server deployed on AWS (EC2 with Docker Compose or ECS Fargate) with admin credentials and HTTPS configured
Anthropic API key for AI-assisted T-SQL to PostgreSQL conversion (or AWS Bedrock access)

Install both ReportBridge apps from the Domo Appstore. Order matters.

Install ReportBridge Admin first — the control plane for configuration, conversion, and publishing.
Install ReportBridge Viewer second. During installation, map its viewer-config DataSet to the Viewer Config DataSet that the Admin app creates in Step 2.
Both apps appear as cards in your Domo instance. Place them on a dashboard for easy access.

Open the ReportBridge Admin card. The Setup Wizard launches automatically on first run.

Create DataSets — auto-creates five Domo DataSets: Config, Catalog, Databases, Audit Log, and Viewer Config.
Connect to Bold Report Viewer — enter hostname, port, site path, and admin credentials. The wizard validates the connection.
Configure the Admin API — enter the Lambda API Gateway URL. The wizard tests connectivity.
Set up AI conversion — provide your Anthropic API key and select the model.
Generate a viewer token — creates an HMAC-signed token (90-day expiry) and writes viewer-safe config. No credentials are exposed to viewer users.

Navigate to the Databases screen. Click Add Database and enter your connection details.

Provide host, port, database name, username, and password. Map to the RDL datasource name.
Add datasource aliases for case variants (e.g., VaVIP_Reporting, VAVIP_Reporting). ReportBridge resolves all variants to a single PostgreSQL connection.
Click Test Connection to verify network access and credentials.
Click Fetch Schemas to load table and column metadata. Schema context is passed to the AI converter for improved accuracy.

Navigate to the Reports screen for individual reports, or the Conversion screen for batch operations.

Upload .rdl files by drag and drop. ReportBridge auto-strips BOM and replaces SQL Server data sources with PostgreSQL connection strings.
Convert — AI rewrites T-SQL to PostgreSQL, tests each query via EXPLAIN, and auto-fixes errors for up to 5 rounds.
Review and fix — use the Test SQL and AI Assist buttons for queries that need manual attention. Expect an 80-90% auto-conversion rate.
Publish — deploys the converted RDL to Bold Report Viewer. Use Batch Convert for bulk operations with progress tracking and ZIP download.

Ensure the viewer is ready to serve reports to your users.

Verify the HMAC-signed viewer token is active (90-day expiry). Regenerate from Settings if needed.
Click Write Viewer Config to push the token, API URL, and Bold Report Viewer host to the Viewer Config DataSet.
Assign Domo groups via Access Control. The Lambda API filters the catalog server-side based on group membership.

Open the ReportBridge Viewer card to see your reports in action.

The sidebar displays report categories. Use the search bar to find specific reports.
Click any report to render it in the embedded viewer with full paginated fidelity.
Reports load inside a Domo Everywhere iframe. No context switching required.

Now that reports are rendering, consider these next steps.

Fine-tune group assignments and per-report visibility rules.

Add more PostgreSQL databases and datasource aliases for new regions.

Track report usage, conversion errors, and API latency in real time.

Rotate viewer tokens, database passwords, and API keys on a regular cadence.