Ideas

Users would benefit from an easy way to set up custom data validations, similar to the setup of consolidation rules. E.g. the amount on a PnL Account needs to match a movement on a BS Account.

By adding Jedox Logs to the OData Hub, users could access the logs from tools like PowerBI instead of the only the console. This would also allow to integrate logs in automation.

This may refer to JS-I-1000. For security purposes I can deactivate the NOSSO url of Jedox Web in order to prevent any user to login without MFA. Meanwhile the OData API and the OLAP server browser can still be accessed without MFA. So I request a...

Sometimes, there are many Legal Entities at customers, paging function would be needed in reports: "Scope of consolidation", "Data collection", "Consolidation Manager", "Consolidated Financial Statement".

The Local GAAP element of the Consolidation dimension is the only element to receive original source data for the separate financial statements. This data is captured on the ~ element of the Scope dimension and shows automatically on all other sco...

Export separate and consolidated financial statements according to one or multiple XBRL based standards (e.g. XBRL, iXBRL, SEC, ESEF, HMRC, etc.).

The sample configuration should be extended by some sample configuration and sample data for notes and according reports

Be able to restrict access to ODATA to certain users/groups independently of access to other Jedox objects.

Sub-consolidation journals using manual consolidation are not reflected in Total Group level. The user expectation is to automatically apply all manual journal entries (Adjustment 1, Transition, Correction or manual consolidation entry) to all sup...

It should be possible, that the jobs in Financial Consolidation Models could run in parallel. The reason is, if you schedule normal jobs e.g. 15 min and they need about 5 min to be finished, and in between you start jobs in financial consolidation...