Skip to Main Content
Jedox Ideas

Let us know how we can make Jedox even better!

Status Shipped
Workspace Jedox Platform
Categories In-Memory DB
Created by Guest
Created on Jul 2, 2019

Aggregation based on attribute values

No description provided
  • ADMIN RESPONSE
    Sep 4, 2020

    We have started development research into implementing the capability to automatically generate aggregations, or hierarchies, based on attribute values for a dimension.

  • Guest
    Reply
    |
    Aug 31, 2021

    Virtual Dimension was shipped as GA in Jedox 2021.3.

  • Admin
    Dominik Lenz
    Reply
    |
    Jun 6, 2020

    We have started development research into implementing the capability to automatically generate aggregations, or hierarchies, based on attribute values for a dimension.

  • Guest
    Reply
    |
    May 28, 2020

    sorry for the many posts. Actually this should not be really a huge challenge since the palo.datav function already returns a vector. I guess that this could be easily summed up internally in the olap server, right ?

  • Guest
    Reply
    |
    May 28, 2020

    Could not it be possible to have a palo.data* function where you could pass arrays instead of single values (similar to palo.datav) and that would sum up the values returned ?

    in this case you could achieve more than just summing up based on attribute values but much more other (based on a subset for instance)

  • Guest
    Reply
    |
    Jul 2, 2019
    Analysis services has so called virtual dimensions to accomplish this.
  • Guest
    Reply
    |
    Jul 2, 2019
    I would also suggest to solve the request by attribute driven hierarchies. From my point of view there are two possibilities: 1. Have an ETL-Load create the hierarchies dynamically based on defined attribute-structures. Example: customer elements have attributes 'Country', 'Region' and 'segment' and two hierarchical structures can be defined: (a) Country | Region | Customer and (b) Segment | Customer 2. (preffered) the dimension structure is configured as in 1., but don't have to be physically loaded into the dimension. Rather they are computed virtually and could be even edited in the Modeller (as a hierarchy of attributes similar to consolidating elements to a hierarchy. Thereby each root defines the virtual dimensions name) In our opinion, this would boost flexibility in analysis of all customers that have few core dimensions with a lot of attributes that they want to explore. As of today in Jedox I have to either create all hierarchies or even create seperate dimensions from the start, giving less flexibility for later analysis and unneccesarily slowing down the system. virtual dimension 2.0 would then allow to decide wheter virtual dimensions can be pivoted against other virtual dimensions of the same physical dimension. In my earlier example that would allow to pivot customer by region vs. segments without having to implement two different dimensions.
  • Guest
    Reply
    |
    Jul 2, 2019
    The comment entered by Admin is not valid. I cannot see how this is covered by Semi Additive Measures (AVG, Last/First Child). Good example is real estate: reporting across different houses which you rent to persons -> Show monthly payments. Each house has a year of construction (Baujahr) and a postal code (PLZ). It would be great to be able to show payments by year of construction and postal Code without defining/updating hierarchies... in a kind of virtual dimension as already proposed. Hierarchies from one dimension for example cannot be combined in a matrix in paste view (one on rows and another on columns) Thanks!
  • Guest
    Reply
    |
    Jul 2, 2019
    IBM added this recently - check out the video here: https://www.youtube.com/watch?v=ZQN3KXuRjBE