Skip to Main Content
Jedox Ideas

Let us know how we can make Jedox even better!

Status Future Consideration
Workspace Jedox Platform
Categories Web Spreadsheet
Created by Guest
Created on Nov 19, 2026

Default Database Selection for an Improved User Experience

Idea / Feature Request

As a power user, I frequently have to manually select the same default database when configuring different components, such as subsets, Dynatables, KPI Cards, Charts, Dynaranges, Comboboxes and palo (data) formulas.

In most customer environments, users primarily work with one or two databases. Therefore, the database they use most frequently should be selected automatically by default when creating new reports or configuring components.

Current Challenge

Currently, selecting the default database requires several repetitive manual steps. This is particularly cumbersome when configuring action buttons:

  1. Right-click the Server/Database icon.

  2. Select Merge Server and Database.

  3. Right-click the icon again.

  4. Select Named Range.

  5. Search the long list for rngDB.

  6. Select rngDB and confirm.

This process has to be repeated even though the same database is used in most cases.

The issue: Users perform many unnecessary clicks to achieve the same result, even though the required database could be preselected automatically.

Proposed Solution

Use the central setting for defining the default database under Administration Settings.

  • Automatic default selection: Whenever a new report or component is created, the system automatically uses the database defined in the administration settings.

  • Dynamic reference: The system should reference the setting (e.g. like rngDB does) rather than writing the actual database name into the component. This ensures that reports, Dynaranges, subsets, and other components continue working if the database name changes.

  • Flexible configuration: If users want to use a different database, they can click an Edit button or icon to override the default and select another database or administration setting.

  • Model-specific configuration: When creating a model, the system should automatically use the database defined in that model's administration settings.

Expected Customer Value

  • Significantly fewer clicks and less repetitive manual configuration.

  • Faster and more efficient report creation.

  • A more consistent user experience across different components.

  • Reduced risk of configuration errors.

  • Easier maintenance when database names change.

Overall benefit: A more intuitive and efficient user experience by automatically applying the user's default database wherever possible, while still allowing flexibility to select a different database when needed.

  • Admin
    Marinella Babutzka
    Nov 19, 2026

    This idea is similar, but describes the problem only for palo formulas: https://feedback.jedox.com/ideas/JS-I-1171