Joining Multiple Report Data Sources Dynamically

In Omniscope Reports you can let viewers drive a join between two (or more) data sources by filtering one source and using the selected values to look up matching records in another.

This technique should not be confused with Omniscope workflow parameters - it is not the same thing. Parameters belong to the Workflow canvas, where they provide run‑time values to transforms. What we describe below happens entirely inside the Report universe and uses ordinary filters, queries and joins.

Scenario

An investment dashboard needs to:

1. Import a user’s portfolio list (e.g. 20 stock tickers).

2. Hold a 30‑year price history table covering every ticker in the market.

3. Show either the total portfolio value or a price‑history chart for any stock the viewer selects.

Step‑by‑Step :

Add the sources to the Report

• Connect both datasets in the Workflow to the Report block.

• They appear in Data Sources as Source 1 (portfolio data) and Source 2 (price history).

Open Report's Sources from the report's toolbar to create a merged source

• Insert a Join block and connect Source 1 and Source 2 to it.

• Join on the shared field [Ticker].

• The Join’s output is automatically labelled Source 3.

Control what flows into the join

• Place a Query block on the Source 1 branch before the join. This query will receive the viewer’s filter selections (e.g. choose one stock or all).

• Add a second Query on the history branch if you also want to limit the date range or other fields.

Expose filters to the viewer

• On the dashboard page, add filter controls on the original sources - typically [Ticker] (from Source 1) and any date or metric filters you placed on Source 2.

• Even though several sources now contain [Ticker], the filters must reference the original inputs (Source 1/Source 2) so that the Queries receive the chosen values.

Build visuals on the merged data

• Point charts that need both portfolio and price information (e.g. a line chart of historical prices) to Source 3.

• Other visuals can still read directly from Source 1 or Source 2 if they do not require the join.

Why this isn’t “parameter passing”

• Parameters are numeric/text values supplied to Workflow blocks at execution time.

• The method above uses standard Report‑level Queries, Filters, and a Join to create a live, interactive relationship between two sources—no parameters involved.

Tips

• Without filters, the join returns every combination of portfolio and history records - be sure to expose at least one device (usually [Ticker]).

• Give Source 3 a meaningful alias (e.g. Portfolio with Prices) for easier selection in visual settings.

• You can extend the pattern to more than two sources - just keep adding queries and joins in series or parallel.

This is how you can create filter‑driven joins inside the Report.

The whole project is available for download below. Should you have any questions - please contact our support@visokio.com