Cross-Version Compatibility of Jedox Components

Jedox provides support for the current and previous releases (including service releases) for up to twelve months after the release of the current version. For more information, see Support Lifecycle. In some cases, Jedox users want to connect different versions of Jedox components with one another, such as an older version of Excel Add-in with the current In-Memory DB (OLAP). This article is meant to be a reference and troubleshooting guide for cross-compatibility of Jedox components.

Known Scenarios

Jedox Support has encountered the following scenarios from customers. Please be aware that even if they work, these scenarios are not officially supported by Jedox. 

Legacy Excel Add-in with current In-Memory DB

In some cases, the user wants to connect an older version of Excel Add-in to a current Jedox In-Memory DB. One reason may be that the server was already updated, but clients were not, as client update is subject to different organizational constraints. This scenario may work, as most parts of the OLAP API are backwards compatible, but Jedox is neither developed nor tested explicitly for this scenario.

Current Excel Add-in with legacy In-Memory DB

Some users want to connect the current Excel Add-in to a legacy server that is not running the current version of Jedox In-Memory DB. This may work, depending on what is actually done, but Jedox is neither developed nor tested explicitly for this scenario.

Current Integrator server with legacy In-Memory DB

Sometimes users want to export data from an older In-Memory DB to a current version of Integrator. This scenario may work, but Jedox has been neither developed nor tested for this circumstance. The success (or lack thereof) of this endeavor depends on the scope and specification of code changes that were implemented between the older and newer versions.  

Current Jedox Web Report with legacy In-Memory DB

Running a current Jedox Web Report that connects to an older version of Jedox OLAP (directly via PALO.DATA function or via macro) may work, as long as the syntax in the report is compatible with the older version of OLAP. For example, a current Web Report containing formulas with flexible cube layout will not work with older OLAP versions, nor will certain API functions inside macros.

Backwards conversion of data (downgrading)

In terms of converting data from current versions of Jedox to older versions, the following principles apply:

  • Once an OLAP database has been loaded with a current version of Jedox, it cannot be loaded with an older version.
  • Imported reports that were exported from a more recent version may work.
  • Imported Integrator projects that were exported from a more recent version may work. The internal definition of Integrator projects can change from version to version. As Jedox Integrator usually migrates project definitions automatically when Jedox is upgraded, it may not be possible to import Integrator projects from current versions of Jedox into older versions.


Both Macro Engine scripts and Supervision Server scripts are written in PHP, and have to be compliant with the PHP version used by Macro Engine and Supervision Server, respectively. They also can make use of Jedox-specific PHP functions, which may be dependent on the Jedox version in use. New versions of Jedox may include new versions of PHP in these two components, and thus may require manual adjustment of script code. Additionally, scripts developed in and working with a current version of Jedox may not work in a previous version.