How do I define a reusable metric in iDBQuery so everyone gets the same number?

You define a metric in iDBQuery's semantic layer and business glossary — for example stating exactly how "net revenue" or "active user" is calculated. Once defined, the AI uses that definition on every relevant question, so the whole team gets one consistent, cited figure instead of conflicting hand-written formulas.

"Revenue" means different things to different people, and inconsistent definitions are how two reports end up disagreeing. iDBQuery lets you settle a definition once.

  • Glossary and semantic layer. Record what a term means and how it should be computed — which columns, which filters, which exclusions. "Net revenue" might be gross minus refunds and tax; "active customer" might require an order in the last 90 days.
  • Applied everywhere. From then on, any question that touches that concept uses your definition, whether it's asked as a number, a chart, or part of a dashboard.
  • Provenance-aware. Definitions merge with what iDBQuery already learned from the schema, so you refine rather than rebuild.

Unlike a traditional BI tool, you don't have to model a full metrics layer up front — you can start chatting immediately and formalise definitions as they matter. For example, once you tell iDBQuery how churn is calculated, everyone from the CEO to a new analyst gets the same churn figure, each answer still cited back to the exact rows so it can be trusted and audited.

Updated 2026-06-22