Documentation Index

Fetch the complete documentation index at: https://knowledge.technolutions.net/llms.txt

Use this file to discover all available pages before exploring further.

The Slate Summit 2026 executive summary is here:  

Using Joinable Bridge in Legacy Queries

Prev Next

🏔️ Summit 2026 Feature

Use Configurable Joins query parts in eligible legacy queries so you can modernize exports and filters without rebuilding the entire query first.

🏗️ Provisional document

This feature is pending release, and this document may change over time. Check What’s New for the latest releases.

Joinable Bridge helps you modernize legacy queries in place. When a legacy query base is enabled for Joinable Bridge, existing queries on that base can use Configurable Joins-style query parts alongside legacy local exports, local filters, and Slate Template Library query parts.

📝 Note

The expanded Joinable Bridge picker appears only for legacy query bases that have been enabled for Joinable Bridge. If the picker shows only Pinned Exports, Local Exports, and Slate Template Library, the base has not been enabled or is not eligible for the bridge.

Before you begin

  • Start with an existing legacy query on a base that has been enabled for Joinable Bridge.

  • Copy critical queries before changing them, especially reports that support daily operations or scheduled exports.

  • Identify the export or filter that you want to replace, supplement, or test with a Configurable Joins query part.

For background on moving legacy query work toward Configurable Joins, see Migrating to Configurable Joins.

Adding bridged query parts to a legacy query

  1. Go to Queries / Reports.

  2. Open an existing legacy query on a base that has been enabled for Joinable Bridge.

  3. Select the Edit Query link.

  4. Select Export or Filter.

  5. Use the Groups section to show the query part sources you want to use.

  6. Select the query part to add.

  7. Configure the query part, then select Save.

  8. Preview or run the query to compare the new query part with existing legacy query parts.

Choosing a query part source

Joinable Bridge adds Configurable Joins query part sources to the legacy query picker. The same general source pattern applies to filters.

  • Local Exports: Legacy exports from the original query base.

  • Library Exports: Query Library exports from the related Configurable Joins base.

  • Direct Exports: Direct fields from the related Configurable Joins base.

  • Extended Exports: Extended Configurable Joins exports that reach related bases.

  • Slate Template Library: Legacy Slate Template Library exports.

Adding a subquery export with a join

Use a subquery export when a legacy query needs an aggregate value or related-record detail that is easier to express with Configurable Joins.

  1. Open the legacy query and select the Edit Query link.

  2. Select Subquery Export.

  3. Enter a descriptive Name.

  4. Configure the following settings:

    • Type: Select the appropriate subquery type, such as Dependent subquery.

    • Output: Select the output type, such as Aggregate.

    • Aggregate: Select the aggregate, such as Count.

  5. Select Join and choose the related base for the subquery.

  6. Add filters or groups as needed.

  7. Select Preview Results to confirm that the query part returns the expected records.

  8. Select Save.

For more information about subquery export settings, see Subquery Exports & Outputs. For more information about joins, see Joins.

Troubleshooting

The expanded groups do not appear

Confirm that the query uses a legacy query base that has been enabled for Joinable Bridge. Legacy queries on bases that are not enabled continue to show the standard legacy query part groups.

The new query part does not return the expected records

Review the join, filters, and subquery type. Then select Preview Results from the query part to confirm which records match before saving the change.

The query result changed after replacing a legacy export or filter

Keep the legacy query part and the new bridged query part side by side while validating the change. After the new query part returns the expected value, remove the old query part if it is no longer needed.

Still looking for what you need?