Best Of

Hi Neha,

Think of "Detail By" as over-riding (for the particular block) whatever you have set in the "Row" axis of the layout.  You could have "Month" in the axis, but if you set "Detail By" to "Year" (for example) for a particular block, then you would see the value of that block by "Year", with any other blocks (that don't have "Detail By" set) shown by "Month".

In your particular case, though, you want a certain block (the "Product Category" Entity) to appear only once, but the other blocks to appear by "Month".  The simplest way to do this is to not put any Entity on the "Row" axis, and then use "Detail By" / "Month" on the other blocks in the layout.  (Note that Board requires the first block in a layout to be a cube, not an entity, so you'd need to just put a cube as block "a" (make sure it's hidden), then your entity as block "b", then followed by the cube that has your values as block "c" (with "Detail By" / "Month").

Try this first, and see how you go.  Sometimes you might want to do a similar thing, but you actually want multiple entities on the "Row" axis (eg. "Year" and "Month") - there's a different trick when this is the case, but I don't want to confuse you too much just yet.  Let me know how you go with the above suggestion first, and if it achieves your desired result.

Cheers,

Craig Parris

Hi Bettina Clausen

You are absolutely correct! When I load to a text cube, the transformation works. Not sure if this how I envisaged the ETL function to work. I thought the transformation layer would transform the data before loading to the target cube. Instead, from what you say and what I have just experienced,  it loads to cube first and then updates the cube by applying the transformation logic. So it is more an ELT  rather than ETL!

In fact before I got your reply, my workaround was to load the data as is to a text cube and the have a data flow to transform to codes and store in another cube.

Thanks,
Dinesh

Davide Genini - fyi