Goeiedag-bonjour, OSI!

Today we'd like to announce two new flashy features, both of which are about breaking down barriers. One is for language barriers, the other one — for interoperability barriers.

Open Semantic Interchange

Export and import semantic layers across tools like Snowflake, Databricks, and others. This way you can easily bring over any model definitions you might have in other tools to Wobby and vice-versa.

OSI is a very new standard, so comaptibility across different vendors may vary. Wobby currently fully supports the OSI 1.0 specification, and we will closely follow any developments to see how we can best implement them.

Five languages, one Wobby

The user interface of Wobby is now translated into five languages — English, Dutch, French, Portugese, and Japanese, with more coming. Wobby Analysts still remain polyglots, and can reply to you in practically any language.

More new features

@mention entities
You can now @mention Semantic Layer entities in messages to Steward and AI Analyst instructions. These mentions keep connection even if you rename the entity.
Data source health monitoring
You will now be promptly notified of any problems with connections to data sources, and have the tools to quickly diagnose and fix them.

Improvements

Keyboard shortcuts in many dialogs
You might see keyboard shortcut hints on many buttons in Wobby soon, helping you move through the interface faster.
Steward's knowledge
We taught Steward a bunch of things, like how to safely replace data sources in models, or how to delete stuff without breaking dependencies.
Geospatial Queries
AI Analysts can now handle geospatial SQL queries with database-specific support (PostgreSQL, etc.). Previously, analysts would incorrectly refuse these requests.

Bug fixes

SemQL compiler now compiles
CTEs, nested aggregations (e.g., MAX(COUNT(...))), and measure references in HAVING clauses now work as they should.
Knowledge graph now graphs
It would sometimes show a blank screen.
Steward no longer says "I'll start working" and then immediately terminates
We won't lie, it was pretty funny. We are, however, sorry if it happened to you — now it shouldn't.
Steward rollback rolls back
It no longer fails with "Reverted 0 entities"
Analysts go the ~~extra~~ mile
Analysis no longer prematurely terminates after 1 iteration with a false "takes too long" warning
...and roughly 20 other bugs too small to explain here

Have a great week, and feel free to send us a quick message if you run into any troubles. Tot ziens!