Attribute view issue

[Former Member]

Hi All,

I created a attribute view with parent child hierarchy within it. I checked the data preview i can able to see the data.

But when i checked the content of the hierarchy attribute in the column view getting a error message "root node id mismatch".

PFB  screenshot for your reference:

Attribute view screenshot.

PAR_CHIL is parent child hierrachy. When i checked the content of the hierarchy attribute (0/TT_P_HI/hier/PAR_CHIL im getting the below error message.

But when i check it for level hierarchy attribute i can able to check the content. The issue is only parent child hierarchy attribute not with the level hierarchy attribute.

Am i missing anything when creating parent child hierarchy?

Please guide me in this.

TIA

[Former Member]

Hi Anooj,

The reason i checked in column view is that i cannot view the analytic view (with parent child hierarchy) in the excel.

Im getting the below error message,

"Excel was unable to get necessary information about this cube. This cube might have reorganised or changed on the server.

Contact the OLAP cube administrator and, if necessary, set up a new datasource to connect the cube."

But when im using with level hierarchy i can view the data in excel.

Thats how i checked the hierarchy column view.

TIA

[Former Member]

Hi All,

Any updates?

[Former Member]

Hi Prasath,

Unfortunately ive not come across this. However, when looking online I found some general information on parent - child hierarchies database checks which return a mismatch output. Perhaps this can be of some use in helping to problem solve the issue:

All mismatch types returned by a system seem to relate to 1 of 4 things:

1) Get Node - The node output - The object to which you want to assign the return value that designates the node ID. The value must be a variable or control with the same data type as the node ID column; a type mismatch will be checked by the runtime engine.

2) Get Node Level - The node ID - The object to which you want to assign the return value that designates the node ID. The value must be a variable or control with the same data type as the node ID column; a type mismatch will be checked the runtime engine.

3) Get Related Node ID - The node ID - The object to which you want to assign the return value that designates the node ID. The value must be a variable or control with the same data type as the node ID column; a type mismatch will be checked by the runtime engine

4) Set Tree Root Node ID - This system function assigns a node ID value to the hidden root node. You can use this system function only if the control has a node ID column. A variable/control with compatible data type (same type as the node ID column) that holds a value. A type mismatch will be checked by the runtime engine.

Based on this try checking that the properties of your attributes are not set to hidden. Check the data types. Check other attribute properties like hierarchy.

Im not able to provide much information but hopefully this is a starting point for further investigation.

Kind regards,

Danielle

[Former Member]

Hi Prasath,

I am on rev 37 and can confirm that I get the same error when I try opening data content on a parent-child hierarchy created on my attribute view. The error message is slight different though - simply says "executor: plan operation execution failed with an exception".

However the same hierarchy works when viewing from an excel (MDX) without a problem. Hence, I am not sure this error while checking data content is actually referring to a problem with the hierarchy that you have created. Have you tried running it from Excel (on the analytic/calc view that uses this attribute view)?

Out of curiosity, why do you want to see the content of this hierarchy type column views & where do you intend to use these column views? The reason why I asked this is because as I understand these hierarchy type column views are created to be used internally by the HANA engines when reporting on the corresponding attr/analytic/calc views. These hierarchy column views are even created on attributes of HANA views where you have not explicity defined any hierarchies.

Thanks,

Anooj