Discussion (4)4
Log in or sign up to continue

Hello Arutunyan,

Can you please clarify a little?  

Maybe add a screenshot or a code snippet of what you are trying to achieve? 




Hi Arutunyan,

Let me know if this properly answers your question. If it does not, please consider adding an example.

We can use the property FullName as an example. Some values for this may be "Gevorg,Arutunyan" or "Steiwer,Peter". You can make a dimension with a source expression using $piece to extract the Last name or the First name. In this case, you may want a single dimension with 2 levels. The first level is "Last Name" that uses the expression: $piece(%source.FullName,",",1). The second level can be called "FirstName" and it can use the expression: $piece(%source.FullName,",",2).

Hi, Peter!

I guess it's more about the source value list type:

We can put this option if the value for the level is a list which provides the way to introduce all the list elements as level members and link the current fact to all of them.

But I was interesting to me too how to manage the second level of hierarchy for such a first level? How Deepsee guesses which list element of the first level have the certain members of the second level and should I show it in expression somehow?

Am I right, Gevorg?



List levels can be confusing because as defined, a single fact can have multiple members. This means that you may see counts higher than the total number of facts in your cube. This can be quite the surprise if you are not expecting it.

Based on the complexity of these types of levels, I would not suggest using them in dimensions with other levels. There may be a particular case where you need this, but I think it would be much safer and a lot more easy to understand if the other levels were placed in different dimensions.