Row Column Intersection in a Cubeview

Dynamics don't aggregate "naturally" like stored accounts, and IsConsolidated has no effect - because there is no number stored, ever, against those accounts/flows/uds. BUT the good news is, now you know how they work, you can simply create your own additions in another UD:

Return api.data.getDataCell("U8#Something + U8#SomethingElse + U8#YetAnother")

Alternatively, if you're after the sum of base Entities, you can "simulate" consolidation in another dynamic (typically on a U8) containing a call to api.Functions.GetEntityAggregationDataCell:

Return api.Functions.GetEntityAggregationDataCell("U8#None")

All of this, like CVC/CVR, will execute at report running time, i.e. for every user every time they look at the related Cube View. If you find this is slow, or you know the CV is executed a lot, it would be better to actually store those calculations, with formulas assigned to a Pass (which is executed during Calculation/Consolidation). That would make aggregation easier, but the rule is a bit more difficult to write, and I'd recommend to take some class first.

Another approach: if your calculations are all simple multiplications, it might be easier to:

1. create a new parent and copy the original members as children (you can do it with None too)
   
2. set the Aggregation Weight for each child, in Relationship Properties, to the factor you're multiplying by:
   

In this way, the parent will contain the aggregation of the original child values multiplied by their individual Aggregation Weight factor, i.e. (Child1 * AW1) + (Child2 * AW2) + (Child3 * AW3) etc.