Introduce Out‑of‑the‑Box Line‑Item Management for Detailed Entry on Cube Intersections

Description:
Jedox currently does not support line‑item level granularity out‑of‑the‑box. When a user needs to enter multiple records on the same dimensional intersection (e.g., multiple transactions for the same Cost Center × Account), the only available workaround is:

• building a custom Line‑Item dimension,

• extending the model accordingly, and

• integrating this dimension into every single load process via Integrator.

This requires complex ETL logic, management of artificial line‑item keys, and maintenance of relationships in every cube load. It also means that a model must be artificially expanded structurally even if line items only apply to selected cubes or selected business processes.

This approach is error‑prone, increases model complexity, and forces customers to solve a very common requirement manually.

Requested enhancement:
Please provide native platform functionality for line‑item management:

1. Ability to store multiple line items at the same dimensional intersection without needing an extra modeling dimension.

2. Support for structured fields per line item (e.g., date, text, amount, tags, category).

3. Built‑in Integrator support for loading and updating line items.

4. Ability to reference and aggregate line‑items seamlessly in reports, Views, and Cube Queries.

5. Optional grouping/aggregation rules (e.g., sum, count, or custom mapping).

6. UI support for entering line items in Web Spreadsheet, Canvas and Excel Add‑ins.

Example use cases:

• Multiple cost entries within the same Cost Center × Account.

• HR cases: several adjustments per employee per period.

• Sales planning: multiple deals, contracts or opportunities per customer.

• Investment planning: several items under the same project and period.

Why this is important:

• Line‑item style input is extremely common in planning & forecasting processes.

• The current workaround (dimension explosion + ETL management) is heavy and fragile.

• A native solution would reduce modeling overhead and ETL complexity dramatically.

• This would bring Jedox closer to tools that already support sub‑entry structures.

Native line‑item management would significantly improve usability, reduce development time and unlock a wide set of detailed planning scenarios - all without burdening models with artificial dimensions.