In the Data Cube connecting to our data warehouse, I have created a calculated measure that displays the operation name, indented based on the level in the hierarchy that it is situated. After I added this measure to the MEASURES section of the Data Analysis Panel, I can see the Operation Name column in my visual table. However, it’s completely blank. I think this is because it’s a string measure instead of a numeric measure. Is there anyway to get a calculated string measure to show as a column in a table?
Get string calculated measure to show on table
Hi Nathan,
If you don’t mind me asking, why do you view this string as a measure, i.e. what are you trying to sum, average, count, etc? If you’re simply trying to count instances of it, you can create it as a dimension but treat it as a measure by specifying count or count distinct for it.
Wayne
We currently have the first column in the table displays the Operation names from multiple levels in the Operation hierarchy of our OLAP cube. They are all left aligned. We would like to add indentation to the names based on the member level so users can quickly distinguish between a region member vs a local member.
In the Data Cube, we can easily do this by creating a calculated string measure call “Operation Name Indented” using Manual MDX script to query data from the cube. The issue we run into is that we can’t display this string measure in the MEASURES section of the Data Analysis Panel. Is there another way to somehow format the different member names based on the level of the hierarchy?
If it were me, I’d make a Dundas hierarchy out of your Operation hierarchy and thereby gain not only automatic indentation but also roll-up on the Dundas side. But I suspect that I am still misunderstanding your situation. In particular, I continue to be thrown off by your desire to have this value show up in the MEASURES section of the Data Analysis Panel because it is a dimensional value, not a measure.
In the end, this is all you’re trying to achieve, isn’t it (i.e. except to replace the date hierarchy on the left with your Operation hierarchy?
1 Like
You can achieve this at the visualization level by setting the Row Header Layout to Single Indented Column
This can be done with both Dundas hierarchies and OLAP hierarchies just the same.
The Operation names auto indented when the dimension comes directly from OLAP data connector, as screenshot below shows.
However, this is not the case when it comes from the Data Cube where Manual Select utilizes MDX script to obtain the data. The indentation format disappeared.
Ah, I see what you mean now. But this makes sense, I think, in that your calculated value is viewed as a simple string instead of a hierarchy, so it loses all automatic formatting, etc. One other clarification: you said in your original post that the Operation Name column was completely blank in your table. Has this problem been solved, such that your only remaining problem is a lack of indentation?