Hi Harm,

Cubes are able to pass on selected row values to connected Tab-Tasks. Is the Task connected to the Table/View that shows the Cube? And does the Cube have a Value column, or only Rows?

Yes it has 2 column fields and 1 data field

This is how the output looks like:

When a Task is connected to the underlying View, you also need to connect the Cube fields/View columns to the Task parameters. This way data of the selected row/value will be put into the connected parameter(s):

This is what I have done, like a regular table with grid view.

I cannot find any additional settings in TSF for thje combination of tasks with cubes

I also see that the Context Procedure is not fired when the dataset is shown visualized as a cube.

Hi Harm,

I may have found the cause. When the PK column(s) is/are not available in the Cube, the connection doesn’t function correctly. For me, I tried it with a Relation table and relation_id (PK) was not present as Cube field. Upon adding that field, the Task parameter was filled in successfully. Can you check that fixes it for you?

Mark,

Finally, it works! I see no reason, why this is reguired for tasks. I have added the missing PK columns to the cube. Not to the cube view, so they are not visible for anybody, which is how we want it. 

I would recommend to add this to the documentation, it took me a lot of time, which cannot be charged to the customer.

Anyways, thanks for your help. 

Best regards, 

Harm

Hi Harm,

Great it solved your problem. I will create a TCP ticket for it to let it be documented.