Feature 02 / 05
Follow related records
Keep the starting record and its joins in view as you move from one question to the next.
DTQL joinsAvailable
The problem
When investigating a customer, order, transaction, or incident, how do you follow it across tables today?
An investigation seldom ends with one row. A customer leads to orders, an order to line items and payments, and a failed payment back to an event. Repeating IDs across tabs and rebuilding joins from memory makes it easy to lose the thread.
A clearer workflow
Anchor the investigation
Begin with the customer, order, transaction, or other identifier you already know.
Trace the relationship
Inspect the keys between tables and build a focused query that returns the related records together.
Keep asking
Refine the query as new evidence appears, without losing the original identifier and join path.
What changes
The relationship becomes part of a repeatable query rather than a sequence of manual lookups.