🖥️Using the Data Model Screen
The Data Model screen serves as your guide to your organization's shared data model along with the integrated BI applications. This feature within our web application is more than a mere tool; it's a robust platform designed to simplify the comprehension of complex relationships and connections within your organization's data structures. The Data Model Screen stands as a comprehensive tool, empowering users to interact with and discover the intricacies of the underlying data structure intuitively.
Resources
This screen is composed of interconnected resources. Every asset in your data model, such as a table, a column in a table, a Chart in your BI tool, or a data transformation, is a resource.
Resources can connect to each other in different ways. For example, a column is a child of a table. A database view can depend on another database view, etc. To learn more about resources and the different ways they can relate to one another, see Relationships.
Universal Resource Identifier (URI)
The Universal Resource Location is the unique identifier for every resource within the mapped data model. The URI is used to map location of resources within the data model, and their connections. To learn more about URIs, see Universal Resource Identifier (URI).
To easily access a URI , open a resource's sidebar and click the "Copy Link" button
located next to the resource's name. This feature allows you to quickly obtain the URL linking to the data model screen and the specific resource. The URI can be found within the URL by removing the initial part: "https://app.euno.ai/data-model?view=graph&highlightedNode=".
The URI can be used to filter out the data model screen by a specific resource, using the URI filter, or it can be used to help diagnose connection mapping issues. In order to diagnose mapping issue between resources view the compiled code, to see the URI referenced in the SQL, and compare it to the parent resource's URI (from its URL). If the two URI do not match, contact customer support for assistance.
Properties
Aside from the identifier, and the relationship to other resources, each resource in Euno has properties. For example:
A table has a name
A column has a data type
A chart in a BI tool has a link
Properties are used to investigate the data model, and can be used as filters to customize which resources are displayed.
Built-in Properties vs. Custom Properties
There are two classes of properties: built-in properties and custom properties. Built-in properties are available for all Euno accounts, and their value is set by the Source integrations. Custom properties are account specific.
Navigation
By default, the Data Model screen displays all Euno resources in a comprehensive table view. Users can filter the data, customize the table by adding or removing relevant fields, download the results, and more.
The Data Model is also where users can access the resource side panel to gain deeper insights into a selected resource or view its lineage in detail.
Filtering & Sorting
The resources on the data model screen can be filtered using any of the available properties, built-in or custom. The basic filter mode allows users to apply simple filters quickly, but it is limited to certain properties and the use of the AND operator between clauses. When multiple filters are applied simultaneously, the operator between them is AND, meaning that all specified criteria must be met for a resource to match the filtered conditions.
For more advanced filtering options, users can switch to EQL mode. In EQL mode, users can leverage advanced query capabilities, explore relationships between resources, and utilize all the available operators and properties for constructing EQL queries. See Using Euno Query Language (EQL). In addition, users can use the "Ask Euno" feature, an AI agent that translates natural language into a searchable EQL statement.
When clicking on a column within the table, the header will display both an action button and a sorting button. From these buttons, users can hide null values, remove the column, or sort the table by the column in either ascending or descending order.
Customizing the Data Model Screen
To customize the tabular view, click on the customize icon 
located at the top-right corner of the table. This will open the customization panel.
The customization panel includes a list of all available fields that can be added to the tabular view. Fields already displayed in the table will be selected, while unselected fields are not currently shown. To add a field, users simply click on it.
A search bar is located at the top of the panel to assist in finding specific fields. The panel also includes actions such as "Select all", "Clear selected", "Restore default", and "Move up". The "Move up" action adjusts the placement of a field within the table. The order of the listed fields determines the order in which they appear in the table.
Additionally, users can drag fields within the table to reorder them, or resize columns by clicking and dragging the divider line in the header.
Viewing a Resource's Lineage
To view a resource’s lineage graph, users can open its side panel—either via the Relationships section or by clicking "Show lineage" in the top-right corner of the panel.
By default, the graph shows only the resource’s immediate upstream and downstream dependencies. Users can expand the graph further using the directional arrows:
<<or>>expands the graph fully in the upstream or downstream direction.<or>reveals only the direct upstream or downstream relationships.
These controls allow users to incrementally explore additional connections. Once clicked, all relevant nodes in the chosen direction will be displayed. If a node has a purple edge, it indicates that more lineage can be revealed in that direction. Note: Expanding the graph only reveals lineage relative to the resource where the expansion was triggered. It does not expand the full lineage for other nodes in the graph. To view a complete lineage graph centered on a different resource, users must open that node’s side panel and initiate a new lineage view.
If the lineage graph is triggered from a non-field-level resource, users will see its upstream and downstream relationships. In EQL, this corresponds to: uri="<resource-uri>")OR has upstream(uri="<resource-uri>")) OR has downstream(uri="<resource-uri>"))
If the lineage graph is triggered from a field-level resource, users will see a slightly different view. This includes field-level upstream and downstream relationships, as well as any downstream visualizations connected to those fields—ultimately showing the dashboards that depend on them. In EQL, this would be represented as: uri="<resource-uri>" OR has upstream_fields(uri="<resource-uri>") OR has downstream_fields(uri="<resource-uri>") OR (type~"dashboard" AND has upstream(has upstream_fields(uri="<resource-uri>")))
In addition, when field-level resources are displayed, they appear under their parent node to provide contextual clarity.
From each node within the graph, users can:
Display additional details by clicking the "Show details" (see #1 in image below) button
Open the node in a new lineage graph, making it the new root node (see #2 in image below)
Or open the side panel of the resource to view its full metadata, including code, usage, lineage, and more (see #3 in image below)
The lineage graph provides an interactive canvas experience. Users can zoom in and out and pan the graph to focus on specific areas. Additionally, users can highlight a specific node to view its path relative to the root node. For example, to trace the path from the root node to another node elsewhere in the graph, users can highlight the secondary node—only nodes within the direct path will be highlighted, while others will be dimmed.
In the bottom-right corner of the graph, a mini-map (see #4 in image below) provides an overview of the entire graph. Users can drag the highlighted area within the mini-map to refocus the main canvas.
In the top-left corner, there is a panel titled "Lineage Insights" (see #5 in image below), which displays connected nodes grouped by resource type. Users can click on a type to expand it, search for specific resources within that group, and then click to highlight a selected resource in the graph.
A search bar (see #6 in image below) is also available in the top-right corner of the graph, allowing users to quickly find and highlight a specific resource. This area also includes a button to center the graph, as well as a button to refocus and highlight the graph on the original node.
A button in the top-right corner of the screen, labeled "Show resources in table view" (see #7 in image below), will open a new window displaying all the resources shown in the lineage graph on the Data Model screen.
Note: Certain resources do not have the option to be viewed in the lineage graph. This applies to resources that are purely containers, such as workbooks, databases, schemas, etc. In addition, certain resources, such as dbt resources, aren't displayed, rather their warehouse.
Side Panel
The side panel is a comprehensive interface for accessing all relevant information about a given resource. Users can open it from the tabular view by clicking on the item, or from the DAG view by using the side panel icon (above the highlighted resource; see image below). Designed to enhance the user experience, it provides insights into relationships, usage, and attributes of data resources. The side panel is divided into a fixed summary bar for quick access and a right-side menu containing the following tabs: Overview, Schema, Used Fields, Contents, Relationships, Usage, and About. However, not all tabs apply to every resource type. The panel dynamically displays the relevant subset based on the type of resource, while the Overview and About tabs are consistently shown for all types. The sections below provide detailed descriptions of each tab's functionality.
Fixed Summary Bar
The Fixed Summary Bar in the Resource Side Panel is designed to keep essential navigation and context elements visible as the user scroll through content and switch between different tabs. This bar includes key elements such as Breadcrumbs, Chips, Automations, View Code, and the Horizontal Ellipses menu, providing quick access to essential features for each resource.
Breadcrumbs
The Breadcrumbs in the Fixed Summary Bar enhance usability by displaying the container chain (parent hierarchy) of the resource, providing users with context and navigational capabilities within the data model hierarchy. Clicking on a specific part of the breadcrumb opens the side panel for that particular resource.
Chips
Chips in the Fixed Summary Bar provide a visual summary of key Built-in Properties for various resource types. Available chips include:
Euno Icon: Appears when a resource is managed by Euno. See Data Model Sync for more details.
Subtype: Indicates the specific subtype of a resource within its general type. For example, under the "table" type, subtypes might include "view," "materialized view," "base table," "temporary table," or "external table." This provides additional context for understanding the nature and behavior of the resource in its data platform.
dbt Materialization Strategy: Indicates the materialization strategy for dbt models as "table," "incremental," "view," "materialized view," or "ephemeral."
Derived View: Applicable to Looker derived views and denotes the derived type, either "SQL Derived View" or "Native Derived View."
Identity Transformation: Displays "Identity Transformation" when the resource has NO inherent logic, and "Contains Logic" when the resource HAS inherent logic.
Calculated: Indicates whether the resource is a calculated field (e.g., a Tableau calculated field or a custom field in Looker).
Instance: Applicable to Tableau embedded data sources, this chip shows "Instance" when the data source is an instance of a published data source.
Defined-by Relationship: If a resource has a defined_by relationship, either as the definer or the definee, chips will be displayed that link directly to the related resources. These chips allow users to easily navigate to the resource(s) that define it or that it defines. For more information, see the relationship; Defined-by.
Automations
If a Euno Automation is available for the resource, it appears in the Automations dropdown within the Fixed Summary Bar. Currently, two automations can be triggered:
Shift Left - For more information see Shift-left Proposals
Add Pre-Aggregations - For more information see Pre-Aggregate Models
Actions
The menu icon (
) in the Fixed Summary Bar offers additional actions to deepen the user’s understanding of the resource:
Open <APP>: Opens the resource in its native application.
View Lineage: Opens a new tab in Graph View displaying the node for the specific resource. By default, it shows the resource's direct upstream and downstream relationships, which can be further expanded to reveal the entire lineage.
Upstream Dependencies: Opens a new tab in the Data Model screen showing all upstream dependencies, helping users understand the origin of the resource and the potential impact of changes.
Downstream Dependencies: Opens a new tab in the Data Model screen showing all downstream dependencies, helping users understand the potential impact of data model changes on other resources.
Impact Analysis: Will trigger a proactive impact analysis to display resource that could potentially be affected by removing or changing it. See Impact Analysis for more details.
View Code
By clicking the code button (</>) located next to the menu button, the resource’s code (if available) will be displayed in the side panel, offering an insightful view into the code that defines the element. The pop-up window containing the transformation code includes a toggle that allows switching between the source and compiled code.
About Section
The first subsection displays the description of the resource, if available, followed by the custom properties. Custom properties are visible in this view, and for fixed properties, users can configure them directly from the side panel. For more information on working with custom properties, see the relevant documentation.
The second subsection includes important details such as the owner of the resource, timestamps for when it was created and last updated, the native ID, Git hosting information (if applicable) such as the repository URI, branch, and revision, and the sponsor or original source from which the resource was ingested.
Metadata & Tags Section
This section displays native metadata and tags from the resource.
Usage & Optimization Section
Table Activities
For resources of type table and for supported sources (currently only Snowflake), Euno displays key usage and cost insights derived from Snowflake’s query history, if made available to Euno (see the Snowflake configuration section for details).
Users can toggle between 14-, 30-, and 60-day timeframes to view:
Storage (for applicable table subtypes):
Storage Cost: The projected cost of storing the table, estimated based on monthly rates and scaled to the selected timeframe.
Volume: The total size of the table in bytes, reflecting how much space it consumes.
Row Count: The number of rows in the table, useful for understanding data scale.
Read Metrics:
Total Read Cost: The estimated cost incurred from querying the table.
Total Read Credits: The number of Snowflake credits consumed by read operations.
Total Read Queries: The total count of queries that read from the table.
Write Metrics (for applicable table subtypes):
Total Write Cost: The estimated cost of write operations on the table.
Total Write Credits: Snowflake credits consumed by inserts, updates, or other write actions.
Total Write Queries: The number of queries that wrote to the table.
Total Write Time: Cumulative time spent executing write operations.
dbt Builds
This subsection is applicable to dbt resources and follows the same 14-, 30-, and 60-day breakdown. It provides insight into model refresh behavior:
Total Builds: Number of times the dbt model was built or refreshed.
Average Build Time: Average duration of a single build, indicating model complexity or runtime.
Total Build Time: Sum of all build durations during the selected period.
Note: This information comes from dbt artifacts uploaded to Euno. If only compiled job data is sent (rather than executed runs), these metrics may not reflect actual build activity.
Usage
The Usage subsection provides comprehensive insights into the usage patterns of each resource, including views, queries, and persistent derived table (PDT) builds, helping users understand how resources are utilized and their relative importance.
Views (Looker Impressions): For specific resources (e.g., Looker Looks and Dashboards), we gather impression data directly from your BI tool to assess activity levels. This data helps determine the relevance of each resource by showing whether associated reports are actively viewed. Users can apply filters like "Total Views 7D" or "Total Views 30D" to narrow down the graph, highlighting resources within your application layer that receive significant attention.
Query Insights: Usage information for key resources and fields (e.g., Looker Looks, Tiles, Dashboards, LookML Views, and the measures and dimensions beneath them; in Tableau: Views, Dashboards, Data Sources, and Workbooks) is derived from query logs in your BI tool or Data Warehouse (DW). This data indicates the frequency of resource and field usage over the last 14, 30, or 60 days, offering insights into their relevance and recent query activity. Users can further explore queried sources to see which reports triggered specific queries and identify users who accessed the data. To streamline analysis, a "Total Queries 14D" filter allows users to focus on the most recent two weeks of activity in the side panel. For a broader overview, the 30-day and 60-day query data can be accessed in the tabular view, enabling a deeper analysis of long-term trends.
Persistent Derived Table (PDT) Builds: For Looker views with a persistent trigger, the Usage tab displays both the total number of PDT builds and the cumulative build time over the last 30 days. This data provides insight into the frequency and total duration of recent PDT refreshes, helping users monitor the processing load and efficiency of these derived tables.
Schema Section
This section presents the resource's schema, organized into sub-resource types: Columns, Dimensions, Measures, and Entities. Each entry (e.g., column, dimension) includes details such as type, shift-left applicability, primary key, and calculated field indicators. Users can click on specific components to open their side panel for a deeper understanding. Additionally, a global search function enables users to quickly find items by name or apply quick filters for more efficient navigation.
Used Fields Section
For visualization resources (e.g., Looker Looks, Looker Tiles, Tableau Views), the Schema section is replaced by the Used Fields tab. This section lists all fields, including calculated fields, actively used within the visualization and mirrors the functionality of the Schema tab, with features like grouping, global search capabilities, and navigation to a component's side panel for detailed insights. This design ensures users can efficiently explore and understand the specific fields involved in their visualizations.
Contents Section
This section is designed for container-type resources that hold other resources, organizing their contents by resource type. A global search function enables users to efficiently find items by name. Users can also select a specific component to open its side panel for more detailed information.
Relationships Section
The first, “Direct Connections,” can be displayed in either a graphical view or a list view, with the graphical view selected by default. In list view, users can search for resources by name. Clicking on a specific resource opens its side panel for additional details. Users can also select specific components to view more information in their respective side panels.
The second subsection, “Insights,” displays the count of all connected resources both upstream and downstream—aggregated by type. Clicking on a tile representing an aggregated type opens the relevant resources in a new tab in the Data Model screen.
Last updated