What’s new in Fusion L2025.2: analytical engine becomes the default

[Community_Admin]

What’s new in Fusion L2025.2: analytical engine becomes the default

In the April 2025.2 release, Sisense will begin using the analytical engine as the default query translator for all new data models.

This is part of a broader modernization effort to improve accuracy, performance, and scalability across the Sisense platform. This year, you’ll see more updates like this as we continue enhancing core functionality, always with a focus on continuity and customer support.

Why we’re making this change

The analytical engine replaces the legacy translator (sometimes called the “heuristic translator”), which has served us for many years but is limited in its ability to support complex models and newer database technologies.

Key reasons for the switch:

• The analytical engine uses structured, dimensional modeling principles for more accurate and optimized query generation
  
  
• It supports a wider range of databases and SQL dialects
  
  
• It delivers faster query performance, especially in Live and Build-to-Destination models
  
  
• It reduces reliance on many-to-many relationships
  
  
• It provides a foundation for long-requested capabilities like outer joins and calculated dimensions

We’ve also added a fallback mechanism so that if a query can’t be handled by the analytical engine, it will automatically revert to the older translator. This ensures minimal disruption while having the benefits of the new engine by default.

What this means for you

• Starting in version L2025.2, the translation engine will be a per-model setting, rather than a system-wide one.
  
  
• All new models will be created with the analytical engine enabled.
  
  
• Existing models will continue to function exactly as they do now, using the current translator unless manually updated.
  
  
• You’ll still be able to opt out and select the legacy translator at the model level during this transition period.
  
  
• Over time, we’ll deprecate the legacy translator, but only after giving you clear guidance and ample time to migrate.
  
  

What’s next

For more information on our analytical engine, check out the documentation. As always, we’ll share more technical guidance, migration support, and documentation as additional updates become available. Stay tuned to the Sisense Community Blog for future posts explaining specific features, how to switch translators, and what to expect in terms of performance or model setup.

In the meantime, we welcome your questions and feedback. Contact Sisense Support or share your experience here in the community.