jan SL rn

website/docs/docs/dbt-versions/release-notes/73-Jan-2024/jan-sl-updates.md

@@ -0,0 +1,35 @@
+---
+title: "dbt Semantic Layer updates and fixes for January 2024"
+description: "January 2024: New Exports feature, conversion metrics, enhanced metrics labels, support for shorthand to create metrics and Tableau parameter filters, and bug fixes."
+sidebar_label: "Updates and fixes: dbt Semantic Layer"
+sidebar_position: 08
+date: 2024-01-31
+---
+The dbt Labs team continues to work on adding new features, fixing bugs, and increasing reliability for the [dbt Semantic Layer](/docs/use-dbt-semantic-layer/dbt-sl).
+
+The following list explains the new features, updates, and fixes for January 2024 in more detail.
+
+## New features
+
+- **Conversion metrics** — 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](/docs/build/conversion).
+- **Introducing Exports** — Use Exports to materialize saved queries within the data platform on a schedule. It uses the dbt Cloud job scheduler to execute saved queries for reliable and fast data reporting.
+- **Simplified dimension resolution** — 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`.
+- **Saved queries** — You can now query the [saved queries](/docs/build/saved-queries) you've defined in the dbt Semantic Layer using [Tableau](/docs/use-dbt-semantic-layer/tableau), [GraphQL API](/docs/dbt-cloud-apis/sl-graphql), [JDBC API](docs/dbt-cloud-apis/sl-jdbc), and the [dbt Cloud CLI](/docs/cloud/cloud-cli-installation).
+
+## Updates
+
+- **Display `label` for dbt Semantic Layer metrics** — The YAML spec parameter `label` is now available for Semantic Layer metrics in [JDBC and GraphQL APIs](/docs/dbt-cloud-apis/sl-api-overview). This means you can conveniently use `label` as a display name for your metrics when exposing them.
+- **Use shorthand to create metrics** — 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.
+- **Support for Tableau parameter filters** — Added support for Tableau parameter filters. You can use the [Tableau connector](docs/use-dbt-semantic-layer/tableau) to create and use parameters with your dbt Semantic Layer data.
+- **Additional parameters for GraphQL API** —  Added support to expose `expr` and `agg` for [Measures](/docs/build/measures) in the [GraphQL API](/docs/dbt-cloud-apis/sl-graphql).
+- **Improved error messages** — When querying a dimension that is not reachable for a given metric, you now have improved error messages returned in the command line interface.
+- **Entities in Tableau** — You can now query entities using our Tableau integration (similar to querying dimensions). 
+- **New Tableau data source** — 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. 
+
+## Bug fixes
+
+- **BigQuery numeric types** — 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.
+- **Support for scientific notation** — Scientific notation for large numbers is displayed and correctly interpreted. 
+- **Google Sheets dimension values** — We now preserve dimension values accurately instead of being inadvertently converted into strings. 
+- **Multiple derived metrics resolution** — 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.
+- **Deduplication of input measures** — 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.