2 Crosstab show the same weeks

[orbair]

Hi all,

I have a report that contains 2 crosstab with 2 different queries. The columns are the weeks. First crosstab has less weeks than the second one, but I want that the second crosstab show only those weeks which are in the first one. Ex

   W1 W2 W3              W1 W2 W3 W4
x  1     3    5            z  3    5    6    9
y  4     5    1            f   4    6    7    8

I would like

   W1 W2 W3              W1 W2 W3
x  1     3    5            z  3    5    6   
y  4     5    1            f   4    6    7   

Thank you in advance for your help.

[orbair]

Can someone please help in this issue? Thank you

[BigChris]

Join the two queries on week?

[orbair]

That is not working well, because my week is a member of Year dimension, and I have error message


GEN-ERR-0016

      The 'currentMember' function is not supported in the context in which it is used.

Thanks

[mel4363]

Hi,

Why don't you have a prompt on weeks that you could select, in this way you can insure that the same weeks are displayed in both crosstabs.

Mel

[MFGF]

That is not working well, because my week is a member of Year dimension, and I have error message


GEN-ERR-0016

      The 'currentMember' function is not supported in the context in which it is used.

Thanks

Hi,

I'm afraid you're not providing anything like enough information to allow us to assist in any meaningful way. This last post seems to indicate you are using a dimensional package? Is that the case? Are the two crosstabs based on the same cube? If so, why not just drag in the desired month members for each?

So:

Are you using a dimensional or relational package?
Do you have a single cube or is each crosstab based on a separate cube?
How are the month columns currently derived or defined in each crosstab?
If the crosstabs are based on the same cube, why are they using different queries - is there a specific reason?
What do the MUNs (Member Unique Names) look like for the Month members?

MF.

[orbair]

Thanks for the reply MFGF. I have resolved this issue meanwhile.