> For the complete documentation index, see [llms.txt](https://docs.euno.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.euno.ai/sources/business-intelligence/cube-core-integration/cube-core-integration-discovered-resources.md). # Cube Core Integration Discovered Resources ## Overview The Cube Core integration discovers the following resources: * Cube deployment (when **Instance slug** is configured) * Cube * Cube view * Cube dimension * Cube measure ## Cube deployment A single resource of type `cube_deployment` is observed when **Instance slug** is set on the source. It groups all cubes and views for that Cube instance. ### Properties | Property | Value | | ----------- | ----------------------------------------------------------------------- | | `type` | always `cube_deployment` | | `name` | Instance display name, or the instance slug when no display name is set | | `native_id` | Configured instance slug | ## Cube Cubes are semantic models defined in Cube schema YAML. Each cube typically maps to a warehouse table through `sql_table`. ### Properties | Property | Value | | ------------------------- | --------------------------------------------------------------------- | | `type` | always `cube_cube` | | `name` | Cube title from schema, or cube name when no title is set | | `native_id` | Cube name from schema | | `description` | Cube description when present in schema | | `raw_code` | YAML fragment for this cube | | `database_technology` | Resolved warehouse technology | | `database_database` | Default database used to qualify unqualified `sql_table` names | | `database_schema` | Default schema used to qualify unqualified table names | | `sql_dialect` | SQL dialect for the resolved warehouse | | `no_compiled_code_reason` | Reason warehouse table lineage could not be resolved, when applicable | Lineage to warehouse tables and joined cubes appears under **Lineage** in the resource sidepane, not as named fields in resource details. ### Relationships * **Parent**: `cube_deployment` (only when **Instance slug** is configured) ## Cube view Views expose subsets or aliases of cube members to consumers. View-scoped dimensions and measures are emitted under the view, not the underlying cube. ### Properties | Property | Value | | ------------- | --------------------------------------------------------- | | `type` | always `cube_view` | | `name` | View title from schema, or view name when no title is set | | `native_id` | View name from schema | | `description` | View description when present in schema | | `raw_code` | YAML fragment for this view | Lineage to underlying cubes appears under **Lineage** in the resource sidepane. ### Relationships * **Parent**: `cube_deployment` (only when **Instance slug** is configured) ## Cube dimension Dimensions are observed under their parent cube or view. ### Properties | Property | Value | | ------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | | `type` | always `cube_dimension` | | `name` | Dimension title from schema, or dimension name when no title is set | | `native_id` | Fully qualified member id (`{cube_name}.{dimension_name}` for cube-scoped members, or view-qualified id for view-scoped members) | | `description` | Dimension description when present in schema | | `raw_code` | YAML fragment for this dimension | | `no_compiled_code_reason` | Reason column-level lineage could not be resolved, when applicable | Field-level lineage to warehouse columns and other cube members appears under **Lineage** in the resource sidepane. ### Relationships * **Parent**: `cube_cube` or `cube_view` ## Cube measure Measures are observed under their parent cube or view. ### Properties | Property | Value | | ------------------------- | ------------------------------------------------------------------------------------------------------------------------------ | | `type` | always `cube_measure` | | `name` | Measure title from schema, or measure name when no title is set | | `native_id` | Fully qualified member id (`{cube_name}.{measure_name}` for cube-scoped members, or view-qualified id for view-scoped members) | | `description` | Measure description when present in schema | | `raw_code` | YAML fragment for this measure | | `no_compiled_code_reason` | Reason column-level lineage could not be resolved, when applicable | Field-level lineage to warehouse columns and other cube members appears under **Lineage** in the resource sidepane. ### Relationships * **Parent**: `cube_cube` or `cube_view` ## Relationships ### Parent / child | Source type(s) | Relationship | Target type(s) | Notes | | -------------------------------- | ------------ | ------------------------ | -------------------------------------------------------- | | `cube_cube`, `cube_view` | has parent | `cube_deployment` | Only when **Instance slug** is configured on the source. | | `cube_dimension`, `cube_measure` | has parent | `cube_cube`, `cube_view` | Members are children of their cube or view. | ### Lineage | Source type(s) | Relationship | Target type(s) | Notes | | -------------------------------- | -------------------- | -------------------------------- | --------------------------------------------------------------------------------------- | | `cube_cube` | has upstream | `table` | Warehouse table from `sql_table` on the cube. | | `cube_cube` | has upstream | `cube_cube` | Joined cubes from `joins` in cube schema. | | `cube_view` | has upstream | `cube_cube` | Underlying cubes referenced by the view. | | `cube_dimension`, `cube_measure` | has upstream\_fields | `column` | Warehouse columns referenced in member SQL, filters, or case branches. | | `cube_dimension`, `cube_measure` | has upstream\_fields | `cube_dimension`, `cube_measure` | Same-cube member references in member SQL, or underlying cube members for view aliases. | {% hint style="info" %} When **Instance slug** is not set, cubes and views use the `default` URI namespace and do not have a `cube_deployment` parent. {% endhint %} --- # 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://docs.euno.ai/sources/business-intelligence/cube-core-integration/cube-core-integration-discovered-resources.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.