Edit dbt models, right in Omni #

Using dbt? Now you can search and view dbt models, run the compiled dbt SQL, and edit your dbt models from inside of Omni.

You can edit existing models or create brand new ones - all you need to do is push the changes to your dbt repository.

Blobby AI got another glow up! #

Our in-app AI helper, Blobby, has some new functionality you can take for a spin. If you’re not sure where to start an analysis, you can ask Blobby what questions you should ask when exploring a topic. Answers will be hyperlinked, and when clicked, will open a new query in the workbook:

And in the near future, Blobby will be able to summarize results for you! For example, you can ask Blobby to identify anomalies in the data, insights into trends, what next steps you should take, and more. Reach out to Omni support if you’re interested in participating in the beta (note that this feature will be opt-in when it becomes available).

Create complex joins with SQL in workbooks #

We added support for creating joins using SQL to the workbook UI. This allows you to create complex joins, such as those that contain conditions:

Color modeling, now for measures #

A few weeks ago, we released color modeling for dimensions. Now you can do the same for measures! 

In a view file, use colors.series to define a color. Then, when the measure is used as a series in a chart, the color will be applied:

Require branches for schema refreshes #

If you want to review schema changes before they’re reflected in a shared model, this new setting is for you. The Branch based schema refresh connection setting requires schema refreshes to be performed in a branch before the changes are promoted to the shared model:

When enabled, schema refreshes can only be triggered from the IDE. If you’re not in an existing branch, selecting Model > Refresh schema will prompt you to create a branch first:

Note: This setting can’t be enabled if a connection has multiple models, or if connection environments (dynamic connections) are currently in use.

Require Pull Requests for system syncs

If you’re using the git integration, you can now require that certain Omni actions have a pull request before they’re committed to your base branch. These actions include schema refreshes, API events, and model syncs.

This setting is located in a model’s git settings, accessed by navigating to Model > Git settings in the IDE:

Note: This setting requires that the Branch based schema refresh setting is also enabled for the connection.

Model usage topic now available in Analytics #

There's a new topic available in your instance's Analytics dashboard. Use it to dive into how models are being used, including how often they're viewed and used in documents:

New organization settings #

We added two new organization settings, accessible in Settings > General:

Here’s how they work:

• Allow invitation requests - When enabled, users can request invitations to the organization from the login page

• Allowed support region - Limits logins from Omni support users to the specified region. When set to something other than All Regions, the support user’s IP address will be checked to ensure it resides in the selected region before they can log in to the organization. Contact Omni support to request access to this feature.

Honorable mentions

But wait, there’s more:

• Dashboard filters and controls can now have descriptions

• The new Microsoft SQL Server Trust Server Certificate connection setting allows Omni to bypass validating the database server’s SSL/TLS certificate

• Non-US dates have new formatting options in charts