Skip to main content

Release - March 14th, 2022

· 3 min read

✨ New ✨#

Homepage#

Details

Product Component

Metrics Catalog

More Detail

Transform has now released our next iteration of the Homepage. This new Homepage has been refocused around Annotations and Subscriptions, providing more rich context about what is happening in a company's data ecosystem, tailored to each individual person at a company. The Homepage is now more of an insights hub, capturing important details about "the why" and helping contextualize what is causing metric values to move.

This new Homepage features Annotations in the left pane. When you click the "see more details" within an Annotation, the card will open to show all metrics affected by the Annotation and how the affected metric values moved during the relevant time range.

The new Homepage also has a set of Subscriptions widgets on the right-hand side of the page that show metric values and their percentage change from the last period.

At the bottom, there is a "Metrics You May Care About" section, containing a set of widgets that enable data consumers to subscribe to new metrics directly inline.

We will continue building out more features into this Homepage and expanding the functionality in the coming weeks, to help bring rich context about what is happening in our customers' data ecosystems.

Verification Steps

Login to Transform and confirm the updates to the homepage.

🐛 Bug Fixes 🐛#

Respect Order With Time Comparison#

Details

Product Component

CLI

More Detail

We have fixed a bug where the order was not being respected when a time comparison was applied.

Verification Steps

Run a query on the CLI like the following:

mql query —metrics metric_name —dimensions ds__day —time-comparison dod —order -ds__day

Time Comparison Gaps Fix#

Details

Product Component

Metrics Framework

More Detail

Snowflake allows for session-level overrides for the start of the week, which means one user might be seeing weekly granularity metrics (or results from other week-based functions) returning with a week start of Monday while another sees a different week start (e.g. Wednesday).

This change brings Snowflake in line with our other engines and ensures consistency across user sessions within an organization by pinning all Snowflake sessions to have WEEK_START set to the ISO standard of Monday. We have pegged the setting to ‘1’ with no available override mechanism, although if such a feature is needed (e.g. customers who wish WEEK_START to be Sunday), we can expose an organization-level configuration setting for it.

For more information on the implications of this change, please refer to the Snowflake documentation on the WEEK_START parameter, how it affects calendar weeks, weekdays and the associated list of affected functions, and examples of how different WEEK_START values might affect output.

Please note that the only customers affected are:

  1. Customers running Snowflake warehouse instances with account or session-level overrides for the WEEK_START parameter that fix it to a value other than 0 or 1. These customers will now see MONDAY as the week start in all cases.
  2. Customers who are using the DAYOFWEEK function inside the expr parameter with the legacy Snowflake default WEEK_START = 0. For these customers, DAYOFWEEK will now return the ISO-standard values of 1 (Monday) through 7 (Sunday) instead of Snowflake’s legacy default values of 0 (Monday) through 6 (Sunday).

Verification Steps

Use a weekly time granularity in the CLI or Metrics Catalog and confirm it uses the ISO standard date.