> For the complete documentation index, see [llms.txt](https://v2.dataos.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://v2.dataos.info/consume/understand/overview.md). # Query After a Data Product is discovered and understood, consumers query its semantic models directly in Studio to confirm that the product exposes the right data for the intended use. In the `Orders Analytics Platform`, querying helps validate customer, sales, and metric data before it is consumed through BI tools, APIs, applications, or saved Perspectives. ## Open Studio From the Data Product page, select **Explore**. The menu shows three options — choose the one that matches how you want to query.

Explore dropdown on the Data Product page showing Visual builder, GraphQL, and Semantic SQL options — Explore dropdown on the Data Product page

## Choose a query workflow Pick the workflow that helps you confirm the shape, fields, and behavior of the result fastest.

Workflow	Use when	Open with
Visual Builder	You want to pick fields, apply filters, and explore data without writing query syntax.	Explore → Visual builder
Semantic SQL	You want to write SQL directly against the semantic model.	Explore → Semantic SQL
GraphQL	You want to write or paste GraphQL when you need full control over the query.	Explore → GraphQL

## What to validate Before consuming a Data Product downstream, use queries to confirm:

Validation	Why it matters
Physical tables are usable	Confirms the raw or curated tables needed for SQL analysis are available and queryable.
Required fields exist	Confirms the semantic model exposes the dimensions or measures needed.
Results match the use case	Confirms the returned rows fit the intended analysis or workflow.
Filters behave correctly	Confirms the query can be scoped to the required business segment, date range, or condition.
Result size is manageable	Confirms the query limit, offset, and export settings are appropriate.
Query can be reused	Confirms whether to save the result as a perspective or API-backed workflow.

## Example flow For an Orders Analytics Platform use case, a consumer can open Studio, add dimensions and measures from the `customer_profile` and `daily_sales` semantic models, run the query, and review the returned rows before reusing them downstream. ## Save the result as a Perspective When a query returns the right result, save it as a Perspective so the same selection can be reused, shared, or consumed through a Data API. See [Perspectives](/consume/understand/overview/perspectives.md) for details. ## Query outcome Querying is complete when the consumer has validated that the required semantic outputs are suitable for the intended use. The next step is to move into the right activation path: BI tools, DB clients, APIs, applications, AI workflows, or a saved Perspective. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://v2.dataos.info/consume/understand/overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.