DataTugPull more from your data
Get started
☰
FeaturesKeep the investigation together

Feature 08 / 08

Keep the investigation together

Keep a database investigation together across related queries and dashboards. Name multiple context bags for environments such as UAT and PROD, apply the one you need, and compare results without mixing inputs.

Context BagIn development

The problem

When one invoice leads to more questions, how do you keep the starting point and environment in view?

An invoice can lead to questions about its line items, customer, and totals. Re-entering identifiers in each query makes it easy to lose the starting point. Mixing records from different environments can make the comparison harder to trust.

A clearer workflow

  1. Start with a known record

    Add Invoice.InvoiceId = 1 to the Context Bag as a typed value, tied to the source and environment you intend to inspect.

  2. Apply a clear revision

    Choose Apply Context when the bag is ready. Later edits create a newer revision; they do not rewrite the input already pinned to a sent turn.

  3. Follow the related records

    Attach and pin the chosen revision to a question. Follow the declared Invoice.InvoiceId → InvoiceLine.InvoiceId relationship, then use the invoice identifier in the line-item query.

  4. Compare named environments

    Use the selected invoice in a dashboard grid and chart. Keep named UAT and PROD bags in the same session, switch the applied bag to compare results, and use separate sessions when you want distinct investigations.

  5. Clear only the active bag

    Choose Clear and confirm. The current context is removed while sent turns and saved runs remain available as history.

  6. Return without re-running

    Reopen the session to review its turns, pinned input, and saved evidence. Queries, dashboards, and Checks run only after an explicit action.

Illustrated workflow

Follow an invoice into its line items

Starting question

Which line items belong to InvoiceId 1?

Steps to follow

  1. Choose a session for the investigation and a Context Bag for the environment, then add Invoice.InvoiceId = 1.
  2. Apply the bag and attach its current revision to the question. Pin that revision before sending the turn.
  3. Use the declared invoice-to-line-item relationship to query InvoiceLine, and review the resulting rows alongside a dashboard grid and chart for the selected invoice.
  4. Keep named UAT and PROD bags in this session and switch the applied bag to compare environments. Use separate sessions for distinct investigations. Clear a bag with Clear and Confirm when you want to remove its active inputs.
  5. Later, reopen the session to review the saved turn and run. Queries, dashboards, and Checks run only after an explicit action.

Evidence to assemble

Context Bag is in development. This is the intended workflow; the painting is an editorial illustration, not a product screenshot or a live demo.

Explore all features

What changes

Related queries, dashboards, and saved evidence stay with the investigation, while named environment bags keep their inputs separate.