Skip to main content
Back to Docs
Under 1 hour

Quick-Start Guide

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

Prerequisites

  • For Domo install: Domo instance with admin access. ReportBridge provides the app bundles and infrastructure — you only need to install the apps and map DataSets.
  • For standalone install: No Domo required. Access ReportBridge at app.report-bridge.com (coming soon).
  • Your SSRS report files (.rdl / .rdlc) — these are uploaded through the admin interface
  • PostgreSQL database with your migrated SQL Server data, accessible over the internet or via VPC peering. ReportBridge provides the Lambda API and report server infrastructure.
  • Network access: your PostgreSQL security group must allow inbound on port 5432 from two IPs that ReportBridge provides during onboarding
1

Install the Apps

Install both ReportBridge apps in your Domo instance. Two options are available:

  • Option A — Domo AppStore (coming soon): Search for ReportBridge and install with one click.
  • Option B — Manual Install (available now): Contact sales@report-bridge.com to receive the app bundles. Create two ProCode apps in Domo, upload the provided manifest.json and bundle.js files, and map the DataSets. Full guide included with the bundles.
  • Standalone mode (no Domo required): Coming soon at app.report-bridge.com. Migrate SSRS reports without a Domo subscription.
2

Run the Setup Wizard

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 the Report Server — 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.
3

Configure Databases

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.
4

Upload and Convert Reports

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 the report server. Use Batch Convert for bulk operations with progress tracking and ZIP download.
5

Configure the Viewer

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 report server host to the Viewer Config DataSet.
  • Assign Domo groups via Access Control. The Lambda API filters the catalog server-side based on group membership.
6

View Reports

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.

What's Next

Now that reports are rendering, consider these next steps.

Access control refinement

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

Additional jurisdictions

Add more PostgreSQL databases and datasource aliases for new regions.

Monitoring via Audit Log + CloudWatch

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

Credential rotation schedule

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