Aggregating data with Data Actions

[chaznosterous52]

Hi experts,

I am currently trying to solve a simple problem for a planning solution, where I have a hierarchy (parent/child) on a dimension, and I want to use a data action to copy values to a different version. The problem arises because I want to aggregate on hierarchy node above the leaf members.

Below is a dummy data version of what I am trying to achieve, but follows the same pattern.

I have been using the following script:

On the following material dimension:

In the script I am using the property “test” to assign the data. But when I run the data action, nothing is assigned and examining the data action monitor, I can see no rows are affected.

I would expect to see the value of amount being assigned to the hierarchy levels TOTAL, ZFURNITURE and ZHIFI.

I have tried to copy all the Member ID’s to the “test” property, which works, but assigns all the data to the leaf levels. I have also tried only keeping the values for TOTAL, ZFURNITURE and ZHIFI in the “test” property, but to no effect.

Does anyone have some pointers in terms of aggregation with Data Actions?

Best regards,

Rasmus

[N1kh1l]

chaznosterous

The reason its not affecting any row is because DATA() and RESULTLOOKUP() only work for base members of dimension. The test attributes has values like ZHIFI and ZFURNITURE which are parent nodes and hence cannot be written back to. If you maintain a base member as attribute value in test it will work.

If you maintain a base member (ZHIFI_D, ZFURNITURE_D etc. ) as attribute value in test it will work.

You need to create this property values also as member first.

Below is the syntax of DATA() and it only accepts leaf members as id/property/parameter/variable member.

DATA([<measures/dimension>=<member_id>,...],[<date_dim>=<date_scope_function>])

<member_id> ::= { <leaf_member> | <#VARIABLEMEMBER> | <parameter_single_leaf> | <dimension> | [<linked_model>.]<dimension> | [<linked_model>.]<dimension>.<property> | ELIMMEMBER() }

Hope this helps !!

Nikhil

[chaznosterous52]

Hi Nikhil,

Thanks for the advice, I tired implementing what you suggested, but I think I might be misunderstanding you (and the documentation)?

Do you mean updating the members of the Material dimension with the ZHIFI_D, ZFURNITURE_D and ZTOTAL_D? Like so:

This makes the script aggregate on the ZHIFI_D, ZFUR_D and ZTOTAL_D for my budget version. However this makes it unviable for disaggregation on the original leaf members, plus they do not display on the rows in a story.

My objective is to aggregate to the ZTOTAL, ZHIFI and ZFURNITURE level and leave the underlying leaf members blank.

Best regards

Rasmus