Skip to main content

dbt Cloud release notes

dbt Cloud release notes for recent and historical changes. Release notes fall into one of the following categories:

  • New: New products and features
  • Enhancement: Performance improvements and feature enhancements
  • Fix: Bug and security fixes
  • Behavior change: A change to existing behavior that doesn't fit into the other categories, such as feature deprecations or changes to default settings

Release notes are grouped by month for both multi-tenant and virtual private cloud (VPC)* environments

* The official release date for this new format of release notes is May 15th, 2024. Historical release notes for prior dates may not reflect all available features released earlier this year or their tenancy availability.

December 2024​

  • New: Auto exposures are now generally available to dbt Cloud Enterprise plans. Auto-exposures integrate natively with Tableau (Power BI coming soon) and auto-generate downstream lineage in dbt Explorer for a richer experience.
  • New: The dbt Semantic Layer supports Sigma as a partner integration, available in Preview. Refer to Sigma for more information.
  • New: The dbt Semantic Layer now supports Azure Single-tenant deployments. Refer to Set up the dbt Semantic Layer for more information on how to get started.
  • Fix: Resolved intermittent issues in Single-tenant environments affecting Semantic Layer and query history.
  • Fix: The dbt Semantic Layer now respects the BigQuery execution_project attribute, including for exports.
  • New: Model notifications are now generally available in dbt Cloud. These notifications alert model owners through email about any issues encountered by models and tests as soon as they occur while running a job.
  • New: You can now use your Azure OpenAI key (available in beta) to use dbt Cloud features like dbt Copilot and Ask dbt . Additionally, you can use your own OpenAI API key or use dbt Labs-managed OpenAI key. Refer to AI integrations for more information.
  • New: The hard_deletes config gives you more control on how to handle deleted rows from the source. Supported options are ignore (default), invalidate (replaces the legacy invalidate_hard_deletes=true), and new_record. Note that new_record will create a new metadata column in the snapshot table.

November 2024​

  • Enhancement: Data health signals in dbt Explorer are now available for Exposures, providing a quick view of data health while browsing resources. To view trust signal icons, go to dbt Explorer and click Exposures under the Resource tab. Refer to Data health signals for resources for more info.
  • Bug: Identified and fixed an error with Semantic Layer queries that take longer than 10 minutes to complete.
  • Fix: Job environment variable overrides in credentials are now respected for Exports. Previously, they were ignored.
  • Behavior change: If you use a custom microbatch macro, set a require_batched_execution_for_custom_microbatch_strategy behavior flag in your dbt_project.yml to enable batched execution. If you don't have a custom microbatch macro, you don't need to set this flag as dbt will handle microbatching automatically for any model using the microbatch strategy.
  • Enhancement: For users that have Advanced CI's compare changes feature enabled, you can optimize performance when running comparisons by using custom dbt syntax to customize deferral usage, exclude specific large models (or groups of models with tags), and more. Refer to Compare changes custom commands for examples of how to customize the comparison command.
  • New: SQL linting in CI jobs is now generally available in dbt Cloud. You can enable SQL linting in your CI jobs, using SQLFluff, to automatically lint all SQL files in your project as a run step before your CI job builds. SQLFluff linting is available on dbt Cloud release tracks and to dbt Cloud Team or Enterprise accounts. Refer to SQL linting for more information.
  • New: Use the dbt_valid_to_current config to set a custom indicator for the value of dbt_valid_to in current snapshot records (like a future date). By default, this value is NULL. When configured, dbt will use the specified value instead of NULL for dbt_valid_to for current records in the snapshot table. This feature is available in the dbt Cloud "Latest" release track (formerly called Versionless) and dbt Core v1.9 and later.
  • New: Use the event_time configuration to specify "at what time did the row occur." This configuration is required for Incremental microbatch and can be added to ensure you're comparing overlapping times in Advanced CI's compare changes. Available in the dbt Cloud "Latest" release track (formerly called Versionless) and dbt Core v1.9 and higher.
  • Fix: This update improves dbt Semantic Layer Tableau integration making query parsing more reliable. Some key fixes include:
    • Error messages for unsupported joins between saved queries and ALL tables.
    • Improved handling of queries when multiple tables are selected in a data source.
    • Fixed a bug when an IN filter contained a lot of values.
    • Better error messaging for queries that can't be parsed correctly.
  • Enhancement: The dbt Semantic Layer supports creating new credentials for users who don't have permissions to create service tokens. In the Credentials & service tokens side panel, the +Add Service Token option is unavailable for those users who don't have permission. Instead, the side panel displays a message indicating that the user doesn't have permission to create a service token and should contact their administration. Refer to Set up dbt Semantic Layer for more details.

October 2024​

 Coalesce 2024 announcements
  • Behavior change: Multi-factor authentication is now enforced on all users who log in with username and password credentials.
  • Enhancement: The dbt Semantic Layer JDBC now allows users to paginate semantic_layer.metrics() and semantic_layer.dimensions() for metrics and dimensions using page_size and page_number parameters. Refer to Paginate metadata calls for more information.
  • Enhancement: The dbt Semantic Layer JDBC now allows you to filter your metrics to include only those that contain a specific substring, using the search parameter. If no substring is provided, the query returns all metrics. Refer to Fetch metrics by substring search for more information.
  • Fix: The dbt Semantic Layer Excel integration now correctly surfaces errors when a query fails to execute. Previously, it was not clear why a query failed to run.
  • Fix: Previously, POST requests to the Jobs API with invalid cron strings would return HTTP response status code 500s but would update the underlying entity. Now, POST requests to the Jobs API with invalid cron strings will result in status code 400s, without the underlying entity being updated.
  • Fix: Fixed an issue where the Source view page in dbt Explorer did not correctly display source freshness status if older than 30 days.
  • Fix: The UI now indicates when the description of a model is inherited from a catalog comment.
  • Behavior change: User API tokens have been deprecated. Update to personal access tokens if you have any still in use.
  • New: The dbt Cloud IDE supports signed commits for Git, available for Enterprise plans. You can sign your Git commits when pushing them to the repository to prevent impersonation and enhance security. Supported Git providers are GitHub and GitLab. Refer to Git commit signing for more information.
  • New: With dbt Mesh, you can now enable bidirectional dependencies across your projects. Previously, dbt enforced dependencies to only go in one direction. dbt checks for cycles across projects and raises errors if any are detected. For details, refer to Cycle detection. There's also the Intro to dbt Mesh guide to help you learn more best practices.
  • New: The dbt Semantic Layer Python software development kit is now generally available. It provides users with easy access to the dbt Semantic Layer with Python and enables developers to interact with the dbt Semantic Layer APIs to query metrics/dimensions in downstream tools.
  • Enhancement: You can now add a description to a singular data test. Use the description property to document singular data tests. You can also use docs block to capture your test description. The enhancement is available now in the "Latest" release track in dbt Cloud, and it will be included in dbt Core v1.9.
  • New: Introducing the microbatch incremental model strategy (beta), available now in dbt Cloud Latest and will soon be supported in dbt Core v1.9. The microbatch strategy allows for efficient, batch-based processing of large time-series datasets for improved performance and resiliency, especially when you're working with data that changes over time (like new records being added daily). To enable this feature in dbt Cloud, set the DBT_EXPERIMENTAL_MICROBATCH environment variable to true in your project.
  • New: The dbt Semantic Layer supports custom calendar configurations in MetricFlow, available in Preview. Custom calendar configurations allow you to query data using non-standard time periods like fiscal_year or retail_month. Refer to custom calendar to learn how to define these custom granularities in your MetricFlow timespine YAML configuration.
  • New: In the "Latest" release track in dbt Cloud, Snapshots have been updated to use YAML configuration files instead of SQL snapshot blocks. This new feature simplifies snapshot management and improves performance, and will soon be released in dbt Core 1.9.
    • Who does this affect? Users of the "Latest" release track in dbt Cloud can define snapshots using the new YAML specification. Users upgrading to "Latest" who have existing snapshot definitions can keep their existing configurations, or they can choose to migrate their snapshot definitions to YAML.
    • Users on older versions: No action is needed; existing snapshots will continue to work as before. However, we recommend upgrading to the "Latest" release track to take advantage of the new snapshot features.
  • Behavior change: Set state_modified_compare_more_unrendered_values to true to reduce false positives for state:modified when configs differ between dev and prod environments.
  • Behavior change: Set the skip_nodes_if_on_run_start_fails flag to True to skip all selected resources from running if there is a failure on an on-run-start hook.
  • Enhancement: In the "Latest" release track in dbt Cloud, snapshots defined in SQL files can now use config defined in schema.yml YAML files. This update resolves the previous limitation that required snapshot properties to be defined exclusively in dbt_project.yml and/or a config() block within the SQL file. This will also be released in dbt Core 1.9.
  • New: In the "Latest" release track in dbt Cloud, the snapshot_meta_column_names config allows for customizing the snapshot metadata columns. This feature allows an organization to align these automatically-generated column names with their conventions, and will be included in the upcoming dbt Core 1.9 release.
  • Enhancement: the "Latest" release track in dbt Cloud infers a model's primary_key based on configured data tests and/or constraints within manifest.json. The inferred primary_key is visible in dbt Explorer and utilized by the dbt Cloud compare changes feature. This will also be released in dbt Core 1.9. Read about the order dbt infers columns can be used as primary key of a model.
  • New: dbt Explorer now includes trust signal icons, which is currently available as a Preview. Trust signals offer a quick, at-a-glance view of data health when browsing your dbt models in Explorer. These icons indicate whether a model is Healthy, Caution, Degraded, or Unknown. For accurate health data, ensure the resource is up-to-date and has had a recent job run. Refer to Data health signals for more information.
  • New: Auto exposures are now available in Preview in dbt Cloud. Auto-exposures helps users understand how their models are used in downstream analytics tools to inform investments and reduce incidents. It imports and auto-generates exposures based on Tableau dashboards, with user-defined curation. To learn more, refer to Auto exposures.

September 2024​

  • Fix: MetricFlow updated get_and_expire to replace the unsupported GETEX command with a GET and conditional expiration, ensuring compatibility with Azure Redis 6.0.
  • Enhancement: The dbt Semantic Layer Python SDK now supports TimeGranularity custom grain for metrics. This feature allows you to define custom time granularities for metrics, such as fiscal_year or retail_month, to query data using non-standard time periods.
  • New: Use the dbt Copilot AI engine to generate semantic model for your models, now available in beta. dbt Copilot automatically generates documentation, tests, and now semantic models based on the data in your model, . To learn more, refer to dbt Copilot.
  • New: Use the new recommended syntax for defining foreign_key constraints using refs, available in the "Latest" release track in dbt Cloud. This will soon be released in dbt Core v1.9. This new syntax will capture dependencies and works across different environments.
  • Enhancement: You can now run Semantic Layer commands commands in the dbt Cloud IDE. The supported commands are dbt sl list, dbt sl list metrics, dbt sl list dimension-values, dbt sl list saved-queries, dbt sl query, dbt sl list dimensions, dbt sl list entities, and dbt sl validate.
  • New: Microsoft Excel, a dbt Semantic Layer integration, is now generally available. The integration allows you to connect to Microsoft Excel to query metrics and collaborate with your team. Available for Excel Desktop or Excel Online. For more information, refer to Microsoft Excel.
  • New: Data health tile is now generally available in dbt Explorer. Data health tiles provide a quick at-a-glance view of your data quality, highlighting potential issues in your data. You can embed these tiles in your dashboards to quickly identify and address data quality issues in your dbt project.
  • New: dbt Explorer's Model query history feature is now in Preview for dbt Cloud Enterprise customers. Model query history allows you to view the count of consumption queries for a model based on the data warehouse's query logs. This feature provides data teams insight, so they can focus their time and infrastructure spend on the worthwhile used data products. To learn more, refer to Model query history.
  • Enhancement: You can now use Extended Attributes and Environment Variables when connecting to the Semantic Layer. If you set a value directly in the Semantic Layer Credentials, it will have a higher priority than Extended Attributes. When using environment variables, the default value for the environment will be used. If you're using exports, job environment variable overrides aren't supported yet, but they will be soon.
  • New: There are two new environment variable defaults — DBT_CLOUD_ENVIRONMENT_NAME and DBT_CLOUD_ENVIRONMENT_TYPE.
  • New: The Amazon Athena warehouse connection is available as a public preview for dbt Cloud accounts that have upgraded to the "Latest" release track.

August 2024​

  • Fix: Fixed an issue in dbt Explorer where navigating to a consumer project from a public node resulted in displaying a random public model rather than the original selection.
  • New: You can now configure metrics at granularities at finer time grains, such as hour, minute, or even by the second. This is particularly useful for more detailed analysis and for datasets where high-resolution time data is required, such as minute-by-minute event tracking. Refer to dimensions for more information about time granularity.
  • Enhancement: Microsoft Excel now supports saved selections and saved queries. Use Saved selections to save your query selections within the Excel application. The application also clears stale data in trailing rows by default. To return your results and keep any previously selected data intact, un-select the Clear trailing rows option.
  • Behavior change: GitHub is no longer supported for OAuth login to dbt Cloud. Use a supported SSO or OAuth provider to securely manage access to your dbt Cloud account.

July 2024​

  • Behavior change: target_schema is no longer a required configuration for snapshots. You can now target different schemas for snapshots across development and deployment environments using the schema config.

  • New: Connections are now available under Account settings as a global setting. Previously, they were found under Project settings. This is being rolled out in phases over the coming weeks.

  • New: Admins can now assign environment-level permissions to groups for specific roles.

  • New: Merge jobs for implementing continuous deployment (CD) workflows are now GA in dbt Cloud. Previously, you had to either set up a custom GitHub action or manually build the changes every time a pull request is merged.

  • New: The ability to lint your SQL files from the dbt Cloud CLI is now available. To learn more, refer to Lint SQL files.

  • Behavior change: dbt Cloud IDE automatically adds a --limit 100 to preview queries to avoid slow and expensive queries during development. Recently, dbt Core changed how the limit is applied to ensure that order by clauses are consistently respected. Because of this, queries that already contain a limit clause might now cause errors in the IDE previews. To address this, dbt Labs plans to provide an option soon to disable the limit from being applied. Until then, dbt Labs recommends removing the (duplicate) limit clause from your queries during previews to avoid these IDE errors.

  • Enhancement: Introducing a revamped overview page for dbt Explorer, available in beta. It includes a new design and layout for the Explorer homepage. The new layout provides a more intuitive experience for users to navigate their dbt projects, as well as a new Latest updates section to view the latest changes or issues related to project resources. To learn more, refer to Overview page.

dbt Semantic Layer​

  • New: Introduced the dbt-sl-sdk Python software development kit (SDK) Python library, which provides you with easy access to the dbt Semantic Layer with Python. It allows developers to interact with the dbt Semantic Layer APIs and query metrics and dimensions in downstream tools. Refer to the dbt Semantic Layer Python SDK for more information.
  • New: Introduced Semantic validations in CI pipelines. Automatically test your semantic nodes (metrics, semantic models, and saved queries) during code reviews by adding warehouse validation checks in your CI job using the dbt sl validate command. You can also validate modified semantic nodes to guarantee code changes made to dbt models don't break these metrics. Refer to Semantic validations in CI to learn about the additional commands and use cases.
  • New: We now expose the meta field within the config property for dbt Semantic Layer metrics in the JDBC and GraphQL APIs under the meta field.
  • New: Added a new command in the dbt Cloud CLI called export-all, which allows you to export multiple or all of your saved queries. Previously, you had to explicitly specify the list of saved queries.
  • Enhancement: The dbt Semantic Layer now offers more granular control by supporting multiple data platform credentials, which can represent different roles or service accounts. Available for dbt Cloud Enterprise plans, you can map credentials to service tokens for secure authentication. Refer to Set up dbt Semantic Layer for more details.
  • Fix: Addressed a bug where unicode query filters (such as Chinese characters) were not working correctly in the dbt Semantic Layer Tableau integration.
  • Fix: Resolved a bug with parsing certain private keys for BigQuery when running an export.
  • Fix: Addressed a bug that caused a "closed connection" error to be returned when querying or running an Export.
  • Fix: Resolved an issue in dbt Core where, during partial parsing, all generated metrics in a file were incorrectly deleted instead of just those related to the changed semantic model. Now, only the metrics associated with the modified model are affected.

June 2024​

  • New: Introduced new granularity support for cumulative metrics in MetricFlow. Granularity options for cumulative metrics are slightly different than granularity for other metric types. For other metrics, we use the date_trunc function to implement granularity. However, because cumulative metrics are non-additive (values can't be added up), we can't use the date_trunc function to change their time grain granularity.

    Instead, we use the first(), last(), and avg() aggregation functions to aggregate cumulative metrics over the requested period. By default, we take the first value of the period. You can change this behavior by using the period_agg parameter. For more information, refer to Granularity options for cumulative metrics.

dbt Semantic Layer​

  • New: Added support for Predicate pushdown SQL optimization in MetricFlow. We will now push down categorical dimension filters to the metric source table. Previously filters were applied after we selected from the metric source table. This change helps reduce full table scans on certain query engines.
  • New: Enabled where filters on dimensions (included in saved queries) to use the cache during query time. This means you can now dynamically filter your dashboards without losing the performance benefits of caching. Refer to caching for more information.
  • Enhancement: In Google Sheets, we added information icons and descriptions to metrics and dimensions options in the Query Builder menu. Click on the Info icon button to view a description of the metric or dimension. Available in the following Query Builder menu sections: metric, group by, where, saved selections, and saved queries.
  • Enhancement: In Google Sheets, you can now apply granularity to all time dimensions, not just metric time. This update uses our APIs to support granularity selection on any chosen time dimension.
  • Enhancement: MetricFlow time spine warnings now prompt users to configure missing or small-grain-time spines. An error message is displayed for multiple time spines per granularity.
  • Enhancement: Errors now display if no time spine is configured at the requested or smaller granularity.
  • Enhancement: Improved querying error message when no semantic layer credentials were set.
  • Enhancement: Querying grains for cumulative metrics now returns multiple granularity options (day, week, month, quarter, year) like all other metric types. Previously, you could only query one grain option for cumulative metrics.
  • Fix: Removed errors that prevented querying cumulative metrics with other granularities.
  • Fix: Fixed various Tableau errors when querying certain metrics or when using calculated fields.
  • Fix: In Tableau, we relaxed naming field expectations to better identify calculated fields.
  • Fix: Fixed an error when refreshing database metadata for columns that we can't convert to Arrow. These columns will now be skipped. This mainly affected Redshift users with custom types.
  • Fix: Fixed Private Link connections for Databricks.

Also available this month:​

  • Enhancement: Updates to the UI when creating merge jobs are now available. The updates include improvements to helper text, new deferral settings, and performance improvements.
  • New: The dbt Semantic Layer now offers a seamless integration with Microsoft Excel, available in preview. Build semantic layer queries and return data on metrics directly within Excel, through a custom menu. To learn more and install the add-on, check out Microsoft Excel.
  • New: Job warnings are now GA. Previously, you could receive email or Slack alerts about your jobs when they succeeded, failed, or were canceled. Now with the new Warns option, you can also receive alerts when jobs have encountered warnings from tests or source freshness checks during their run. This gives you more flexibility on when to be notified.
  • New: A preview of the dbt Snowflake Native App is now available. With this app, you can access dbt Explorer, the Ask dbt chatbot, and orchestration observability features, extending your dbt Cloud experience into the Snowflake UI. To learn more, check out About the dbt Snowflake Native App and Set up the dbt Snowflake Native App.

May 2024​

  • Enhancement: We've now introduced a new Prune branches Git button in the dbt Cloud IDE. This button allows you to delete local branches that have been deleted from the remote repository, keeping your branch management tidy. Available in all regions now and will be released to single tenant accounts during the next release cycle.

dbt Cloud Launch Showcase event​

The following features are new or enhanced as part of our dbt Cloud Launch Showcase event on May 14th, 2024:

  • New: dbt Copilot is a powerful AI engine helping you generate documentation, tests, and semantic models, saving you time as you deliver high-quality data. Available in private beta for a subset of dbt Cloud Enterprise users and in the dbt Cloud IDE. Register your interest to join the private beta.

  • New: The new low-code editor, now in private beta, enables less SQL-savvy analysts to create or edit dbt models through a visual, drag-and-drop experience inside of dbt Cloud. These models compile directly to SQL and are indistinguishable from other dbt models in your projects: they are version-controlled, can be accessed across projects in dbt Mesh, and integrate with dbt Explorer and the Cloud IDE. Register your interest to join the private beta.

  • New: dbt Cloud CLI is now Generally Available (GA) to all users. The dbt Cloud CLI is a command-line interface that allows you to interact with dbt Cloud, use automatic deferral, leverage dbt Mesh, and more!

  • New: The VS Code extension Power user for dbt Core and dbt Cloud is now available in beta for dbt Cloud CLI users. The extension accelerates dbt and SQL development and includes features such as generating models from your source definitions or SQL, and more!

  • New: Unit tests are now GA in dbt Cloud. Unit tests enable you to test your SQL model logic against a set of static inputs.

  •  New: Native support for Azure Synapse Analyticspreview

  • New: MetricFlow enables you to now add metrics as dimensions to your metric filters to create more complex metrics and gain more insights. Available for all dbt Cloud Semantic Layer users.

  • New: Staging environment is now GA. Use staging environments to grant developers access to deployment workflows and tools while controlling access to production data. Available to all dbt Cloud users.

  • New: Oauth login support via Databricks is now GA to Enterprise customers.

  •  New: GA of dbt Explorer's features

  • New: Native support for Microsoft Fabric in dbt Cloud is now GA. This feature is powered by the dbt-fabric adapter. To learn more, refer to Connect Microsoft Fabric and Microsoft Fabric DWH configurations. There's also a quickstart guide to help you get started.

  • New: dbt Mesh is now GA to dbt Cloud Enterprise users. dbt Mesh is a framework that helps organizations scale their teams and data assets effectively. It promotes governance best practices and breaks large projects into manageable sections. Get started with dbt Mesh by reading the dbt Mesh quickstart guide.

  • New: The dbt Semantic Layer Tableau Desktop, Tableau Server, and Google Sheets integration is now GA to dbt Cloud Team or Enterprise accounts. These first-class integrations allow you to query and unlock valuable insights from your data ecosystem.

  • Enhancement: As part of our ongoing commitment to improving the dbt Cloud IDE, the filesystem now comes with improvements to speed up dbt development, such as introducing a Git repository limit of 10GB.

Also available this month:​

  • Update: The dbt Cloud CLI is now available for Azure single tenant and is accessible in all deployment regions for both multi-tenant and single-tenant accounts.

  • New: The dbt Semantic Layer introduces declarative caching, allowing you to cache common queries to speed up performance and reduce query compute costs. Available for dbt Cloud Team or Enterprise accounts.

  •  New: Latest Release Track

  • Behavior change: Introduced the require_resource_names_without_spaces flag, opt-in and disabled by default. If set to True, dbt will raise an exception if it finds a resource name containing a space in your project or an installed package. This will become the default in a future version of dbt. Read No spaces in resource names for more information.

April 2024​

  •  New: Merge jobsbeta

  • Behavior change: Introduced the require_explicit_package_overrides_for_builtin_materializations flag, opt-in and disabled by default. If set to True, dbt will only use built-in materializations defined in the root project or within dbt, rather than implementations in packages. This will become the default in May 2024 (dbt Core v1.8 and dbt Cloud release tracks). Read Package override for built-in materialization for more information.

dbt Semantic Layer

  • New: Use Saved selections to save your query selections within the Google Sheets application. They can be made private or public and refresh upon loading.
  • New: Metrics are now displayed by their labels as metric_name.
  • Enhancement: Metrics now supports the meta option under the config property. Previously, we only supported the now deprecated meta tag.
  • Enhancement: In the Google Sheets application, we added support to allow jumping off from or exploring MetricFlow-defined saved queries directly.
  • Enhancement: In the Google Sheets application, we added support to query dimensions without metrics. Previously, you needed a dimension.
  • Enhancement: In the Google Sheets application, we added support for time presets and complex time range filters such as "between", "after", and "before".
  • Enhancement: In the Google Sheets application, we added supported to automatically populate dimension values when you select a "where" filter, removing the need to manually type them. Previously, you needed to manually type the dimension values.
  • Enhancement: In the Google Sheets application, we added support to directly query entities, expanding the flexibility of data requests.
  • Enhancement: In the Google Sheets application, we added an option to exclude column headers, which is useful for populating templates with only the required data.
  • Deprecation: For the Tableau integration, the METRICS_AND_DIMENSIONS data source has been deprecated for all accounts not actively using it. We encourage users to transition to the "ALL" data source for future integrations.

March 2024​

  • New: The Semantic Layer services now support using Privatelink for customers who have it enabled.
  • New: You can now develop against and test your Semantic Layer in the Cloud CLI if your developer credential uses SSO.
  • Enhancement: You can select entities to Group By, Filter By, and Order By.
  • Fix: dbt parse no longer shows an error when you use a list of filters (instead of just a string filter) on a metric.
  • Fix: join_to_timespine now properly gets applied to conversion metric input measures.
  • Fix: Fixed an issue where exports in Redshift were not always committing to the DWH, which also had the side-effect of leaving table locks open.
  • Behavior change: Introduced the source_freshness_run_project_hooks flag, opt-in and disabled by default. If set to True, dbt will include on-run-* project hooks in the source freshness command. This will become the default in a future version of dbt. Read Project hooks with source freshness for more information.

February 2024​

  • New: Exports allow you to materialize a saved query as a table or view in your data platform. By using exports, you can unify metric definitions in your data platform and query them as you would any other table or view.

  • New: You can access a list of your exports with the new list saved-queries command by adding --show-exports

  • New: The dbt Semantic Layer and Tableau Connector now supports relative date filters in Tableau.

  •  New: Use exports to write saved queries
  •  New: Trigger on job completion teamenterprise
  •  New: Latest Release Trackbeta
  •  New: Override dbt version with new User development settings
  •  Enhancement: Edit in primary git branch in IDE

  • Enhancement: The dbt Semantic Layer Google Sheets integration now exposes a note on the cell where the data was requested, indicating clearer data requests. The integration also now exposes a new Time Range option, which allows you to quickly select date ranges.

  • Enhancement: The GraphQL API includes a requiresMetricTime parameter to better handle metrics that must be grouped by time. (Certain metrics defined in MetricFlow can't be looked at without a time dimension).

  • Enhancement: Enable querying metrics with offset and cumulative metrics with the time dimension name, instead of metric_time. Issue #1000

    • Enable querying metric_time without metrics. Issue #928

  • Enhancement: Added support for consistent SQL query generation, which enables ID generation consistency between otherwise identical MF queries. Previously, the SQL generated by MetricFlowEngine was not completely consistent between identical queries. Issue 1020

  • Fix: The Tableau Connector returns a date filter when filtering by dates. Previously it was erroneously returning a timestamp filter.

  • Fix: MetricFlow now validates if there are metrics, group by, or saved_query items in each query. Previously, there was no validation. Issue 1002

  • Fix: Measures using join_to_timespine in MetricFlow now have filters applied correctly after time spine join.

  • Fix: Querying multiple granularities with offset metrics:

    • If you query a time offset metric with multiple instances of metric_time/agg_time_dimension, only one of the instances will be offset. All of them should be.
    • If you query a time offset metric with one instance of metric_time/agg_time_dimension but filter by a different one, the query will fail.

  • Fix: MetricFlow prioritizes a candidate join type over the default type when evaluating nodes to join. For example, the default join type for distinct values queries is FULL OUTER JOIN, however, time spine joins require CROSS JOIN, which is more appropriate.

  • Fix: Fixed a bug that previously caused errors when entities were referenced in where filters.

January 2024​

  •  January docs updates

  • New: New metric type that allows you to measure conversion events. For example, users who viewed a web page and then filled out a form. For more details, refer to Conversion metrics.

  • New: Instead of specifying the fully qualified dimension name (for example, order__user__country) in the group by or filter expression, you now only need to provide the primary entity and dimensions name, like user__county.

  • New: You can now query the saved queries you've defined in the dbt Semantic Layer using Tableau, GraphQL API, JDBC API, and the dbt Cloud CLI.

  •  New: Native support for partial parsing

  • Enhancement: The YAML spec parameter label is now available for Semantic Layer metrics in JDBC and GraphQL APIs. This means you can conveniently use label as a display name for your metrics when exposing them.

  • Enhancement: Added support for create_metric: true for a measure, which is a shorthand to quickly create metrics. This is useful in cases when metrics are only used to build other metrics.

  • Enhancement: Added support for Tableau parameter filters. You can use the Tableau connector to create and use parameters with your dbt Semantic Layer data.

  • Enhancement: Added support to expose expr and agg for Measures in the GraphQL API.

  • Enhancement: You have improved error messages in the command line interface when querying a dimension that is not reachable for a given metric.

  • Enhancement: You can now query entities using our Tableau integration (similar to querying dimensions).

  • Enhancement: A new data source is available in our Tableau integration called "ALL", which contains all semantic objects defined. This has the same information as "METRICS_AND_DIMENSIONS". In the future, we will deprecate "METRICS_AND_DIMENSIONS" in favor of "ALL" for clarity.

  • Fix: Support for numeric types with precision greater than 38 (like BIGDECIMAL) in BigQuery is now available. Previously, it was unsupported so would return an error.

  • Fix: In some instances, large numeric dimensions were being interpreted by Tableau in scientific notation, making them hard to use. These should now be displayed as numbers as expected.

  • Fix: We now preserve dimension values accurately instead of being inadvertently converted into strings.

  • Fix: Resolved issues with naming collisions in queries involving multiple derived metrics using the same metric input. Previously, this could cause a naming collision. Input metrics are now deduplicated, ensuring each is referenced only once.

  • Fix: Resolved warnings related to using two duplicate input measures in a derived metric. Previously, this would trigger a warning. Input measures are now deduplicated, enhancing query processing and clarity.

  • Fix: Resolved an error where referencing an entity in a filter using the object syntax would fail. For example, {{Entity('entity_name')}} would fail to resolve.

0
Edit this page