✨ New ✨
Collections
Details
Product Component
Metrics Catalog
More Detail
Both individuals and teams often want to group together the most important metrics that apply to their job function. Transform provides the metrics in the UI that you can click into individually, which is helpful and all, but you have to click back and forth between different metrics if you want to look at multiple. Wouldn't it be nice to be able to see a handful of your key metrics in one place? Well, I'm so glad you're wondering... because now you can! We've introduced Collections! Collections allow you to group all your important metrics in one place.
You can associate collections to yourself, or to a team, which will show up on the Team Pages.
Verification Steps
- Navigate to the Collections menu in the sidebar and choose "Make your Collection"
- Fill in information about your collection
- Create Collection by adding Metrics
- View your Collection and add other metrics by using the "edit" button.
- Be Excited!
Saved Queries
Details
Product Component
Metrics Catalog
More Detail
Have you ever wanted to revisit a dimensional slice and grouping of a metric that you previously created in Transform without having to select all the filters and groups again? Us too! This is why we introduced Saved Queries.
Not only will this feature allow you to save common queries and go back and analyze results without re-creating the filter, but it also allows other users to see common queries against metrics and learn more about what might be important to look at for a particular metric.
Verification Steps
- To create a saved query, go to the main metric page chart and hit "edit chart". Select your filters and groupings that you desire.
- Save the query by clicking on "More Actions". Title and Save the query associated with yourself or a Team. Note: anyone can see this query in either selection, but if you add it to a Team page, it will also show up on the respective Team Page under "Saved Queries"
- Access your Queries associated with Metrics by Clicking on the "Queries" tab. A count is provided so you can see which metrics are the "cool kids" for queries.
Team Pages
Details
Product Component
Metrics Catalog
More Detail
Have you ever been itching to view all your Team's important metrics, queries, and collections in one place? Collaboration with your teams is crucial to building a data culture at your company, and our mission at Transform is to empower you to do that, which is why we introduced the concept of Team Pages.
Team Pages allow you to create a team in Transform, add members to it, and all collaborate on a page that has your key metrics, collections, and saved queries.
Verification Steps
- You can find team pages on the lefthand menu
- To create a team, select "Create a Team" which will take you to the following page to ask you the team name, members, and description. You can always edit teams in the Settings menu as well under " Manage Teams"
- Access your Team Page listed in the lefthand menu.
New Chart Menu with Export CSV
Details
Product Component
Metrics Catalog
More Detail
We added a new chart menu that allows you to Export as CSV, Download full screen, or go into the query logs for that particular query.
I was trying to come up with a good CSV joke, but I struggled because they are Comedy-Limited 😏
Verification Steps
Go into any metric chart. This can be accessed through a metric page, or even on the homepage. Select the three dots on the top of the graph and select the desired option.
Additional Chart Actions
Details
Product Component
Metrics Catalog
More Detail
We've added a few additional chart actions when editing a chart or query so that users know when the chart data properly reflects their changes.
We also added options to revert back to original filters during an editing process and actions around updating a saved query.
Verification Steps
- Go into a metrics data chart
- Choose Edit Chart and make some changes to the filters. You should notice that the Chart prompts you to update or revert (previously, the chart would show un-updated data and so it wasn't clear whether the chart was showing new or old information)
- Scroll down and find the new action menu, which will have information about resetting filters, clearing filters, saving as a query, or updating a query if you're editing a Saved Query.
Export to CSV from CLI
Details
Product Component
Interfaces - MQL CLI
More Details
🎉 You can now export query results directly to a csv file using the Transform CLI.
This accompanies the feature in the UI to export a CSV.
Verification Steps
$ mql query --metrics bookings --dimensions ds --order ds --csv ~/Desktop/bookings.csv
✔ Query initialized: 1622140544978_0000007
✔ Success 🦄 - query completed after 2.24 seconds
Successfully written query output to /Users/marco/Desktop/bookings.csv
Added Display Name when Creating Metric from Measure
Details
Product Component
Metrics Framework
More Detail
We added the ability to create a metric directly when creating a measure. When you create a metric from a measure, there was no mechanism to configure a display name, so we added a new argument called create_metric_display_name
Verification Steps
If you create a metric from a measure, you can add the argument and confirm that it shows up with a "pretty" name in the UI.
For example:
name: api_requests
expr: "1"
agg: sum
create_metric: true
create_metric_display_name: API Requests
🐛 Bug Fixes 🐛
Dimension Values spanning multiple data sources
Details
Product Component
Metrics Framework
More Detail
Previously, we would throw an error when looking at dimensions if you had a metric that had two measures that came from different data sources, one where the dimension was local and one where it was non-local.
Verification Steps
Create a metrics configuration that has two different data sources. The metric should contain two measures - one that is local to the data source containing the requested dimension and one that is non-local.
For Example:
Assume you have a metric called bookings that has information from two different data sources, X and Y.
You might have a dimension called country from data source X that is non-local to the primary identifier, so it needs to be joined onto another identifier, such as listing to obtain the values (e.g., listing__country)
The booking metrics may have another measure from Data Source Y that has the country dimension locally, e.g., simply country. The discrepancy was that our query builder assumes dimensions will be accessed by name, and so we were unable to retrieve data source X and data source Y to retrieve the dimension values for the country by the bookings metric because listing__country != country.