Ideas

When creating a json extract the different column names can be defined. This would be great that it does not have to be defined manually but dynamically, I see 2 possibilities: 1/ getting the column list from another extract or transform 2/ have a...

Currently, we use the standard description fields in integrator projects, cubes, and dimensions for 2 purposes: 1.) General information about the structure and function of the project or cube/dimension 2.) Documentation of changes (2025/03/17 John...

With the new Jedox mobile app (old app had a zoom function), you aren't able to zoom in or out on a large report designed from the Web. So as a workaround you have to create separate "mobile" reports (so one report for Jedox Web and a separate one...

Currently, when creating a new Extract within the Integrator, the system automatically generates a default name, such as "New Excel Extract." However, given the varying preferences of consultants, it would be beneficial to offer users the option t...

Major clouds have Amazon Web Services（AWS） Microsoft Azure（Azure） Google Cloud Platform（GCP） Currently Jedox Integrator only have Azure connection. Similar to Azure, a new connection type to AWS(S3 etc) , GCP should be offered.

At one of our prospects, we ran into a requirement, where prospect files are located in Google Drive. Since cloud solutions are spreading, it will be a more and more frequent required functionality to access these cloud-based file servers. If it i...

It would be great to be able to change the default of a variable in the overview of all existing variables instead of having to to click/open every single variable to make changes. In addition it could be useful to change the description here as w...

Would it be possible to see when an object in the integrator is created and last modified?

With Jedox mobile, you can zoom in on a large report designed from the Web but you can't zoom out to see the entire report.

At the moment, Jedox differentiates between uppercase and lowercase in the integrator and treats the elements like two different ones. Example: RepUnit <> REPUNIT -> Table normalization, lookups etc. won't work properly as Jedox raises th...