Documentation Index

Fetch the complete documentation index at: https://docs.turbo360.com/llms.txt

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

Querying transaction instances

  • 5 minute(s) read
Prev Next

Overview

Querying transaction instances in the Data Queries type lets you search and filter tracking data using the column-based WHERE syntax specific to the Data Queries BAM model. Query data is sourced from the query defined for each transaction during the configuration process, not from a shared SQL database.

Business value

The Data Queries tracking interface gives you targeted visibility into the specific data columns your transactions expose. This allows you to filter and locate transaction instances without relying on the broader DSL available in the Custom Logging type, keeping queries scoped to the data your transaction query actually returns.

Prerequisites

Required permissions

Action Required permission
View saved queries View saved queries
Save, edit, delete, and set a default query Manage saved queries

How it works

Query data available for execution will be sourced from the query defined for a particular transaction during the creation process.

In the Data Queries type, you can query only the columns available in the transaction query data. The query syntax uses a WHERE-style statement:

{column name} {condition} {value}

Before running a query, use the Select transaction dropdown to choose the transaction whose data you want to search. The query runs against the data returned by that transaction's configured query.

Advanced search options available in the Custom Logging type — such as searching for assigned transactions, global properties, wildcard characters, and advanced multi-value queries — are not available in the Data Queries type.

The Tracking tab displays results in a grid. Each row represents one transaction instance returned by the configured data source query. The columns shown depend on what the transaction's query returns — common columns include TenantId, TimeGenerated, Message, and SeverityLevel. Click the arrow icon on a row or use the Actions menu to open the full instance details.

Steps

Use the following steps to run queries and manage saved queries in the Tracking section. Navigate to Business Activity Monitoring > your business process > Tracking to get started.

Run a query

Running a query retrieves transaction instances from your configured data source within a specified time range.

  1. Select a transaction from the Select transaction dropdown. Only transactions configured within the current business process are available.
  2. Set the time range using the Started from dropdown. Options include preset periods (such as Last 1 hour, Last 24 hours) and Custom, which activates a date range bar where you can enter an explicit start and end date and time.
  3. Set the Select top value to limit the number of results returned. The default is 1000.
  4. Optionally, enter a filter expression in the Enter the query field using the WHERE-style syntax:
    {column name} {condition} {value}
    Leave the field empty to return all instances within the selected time range and top limit.
  5. Click Search.

Results appear in the grid below. Each row is one transaction instance. To inspect an instance, click the arrow icon on the row or click the Actions menu and select View transaction details.

[MISSING INFORMATION: screenshot of Tracking tab showing Select top, Started from, Select transaction, and Enter the query fields with a results grid]

Save a query

Saving a query stores your column-based search criteria so you can reuse it without re-entering parameters each session.

  1. Select a transaction from the Select transaction dropdown.
  2. Run a query for the required time period.
  3. Click the dropdown arrow next to Save and select an option:
    • Save — saves the query under its current name. Use this to update an existing saved query.
    • Save As — saves the query as a new entry. Use this when saving a query for the first time or creating a variant of an existing one.
  4. Enter a name for the query and click Save.

You can access saved queries using the Saved queries option at the top of the Tracking page. You can also set a query as the default by selecting the checkbox in the save blade.

If you do not provide a name, the query receives an auto-generated name based on the current time and date.

Import or export a query

Importing and exporting queries lets you reuse saved query definitions or share them with other users.

  • To import: click Import in the Saved queries blade and select a downloaded query file in JSON format.
  • To export: click Export in the Saved queries blade to download the saved query as a JSON file.

Lock a query

Locking a saved query prevents other users from editing or deleting it until the lock is released.

  1. Open Saved queries.
  2. Click the Actions menu next to the query you want to lock.
  3. Select Lock.
  • You need Manage saved queries permission to lock or unlock a query.
  • A locked query can only be unlocked by the user who locked it, or by users with the Owner or Account owner permission.

Configuration

Field Description
Select top Maximum number of instances to return. Defaults to 1000. Reduce this for faster queries on large datasets.
Started from Time range for the query. Choose a preset period or Custom to set an explicit start and end date and time.
Select transaction The transaction whose data source query defines the columns and data available for filtering.
Enter the query Optional WHERE-style filter: {column name} {condition} {value}. Leave empty to return all results within the time range and top limit.

Limitations

  • The Data Queries type supports only the column WHERE syntax for querying. Wildcard characters, global property searches, advanced multi-value queries, and assigned transaction queries are not available.
  • Query data is scoped to the columns returned by the transaction's configured data source query — you cannot query columns outside that result set.
  • The Select top limit applies before any filter expression. If results are limited by the top value, matching instances outside that window will not be returned.

Troubleshooting

  1. Query returns no results
    Cause: The column name used in the query does not match the column names returned by the transaction's data query, or no data exists in the selected time range.
    Fix: Review the transaction configuration to confirm the exact column names available in the query result set. Widen the time range and try again.

  2. Started from dropdown shows no Custom option
    Cause: The transaction may not be selected yet — the time range controls activate after a transaction is chosen.
    Fix: Select a transaction from the Select transaction dropdown first, then set the time range.

  3. Saved query is missing after another user runs a search
    Cause: Saved queries are personal to the user who created them.
    Fix: Export the query as a JSON file and share it with the other user, who can then import it via the Saved queries blade.

  4. Import fails for a query exported from a Custom Logging transaction
    Cause: Custom Logging query files may reference properties or syntax not supported in the Data Queries type.
    Fix: Create a new query directly in the Data Queries Tracking interface rather than importing from a Custom Logging query file.

  5. Lock option is not visible on a saved query
    Cause: You do not have the Manage saved queries permission.
    Fix: Ask your BAM administrator to grant the required permission.

Related articles