Composite datawindow with retrieval argument

[Former Member]

Hi All,

I have come across a situation in which my client needs a crosstab report in single report for every row from the master table. In this case the cross tab would vary based on products.

Since Crosstab with retrieval argument can only be used in composite kind of datawindow, i have been in search for a workaround.

Kindly suggest.

Thanks

[Former Member]

Hi Franklin,

Always helps to read the question more than once... You asked for a workaround:

Place the crosstab report with arguments in a new composite report with identical arguments, pass them on from composite to crosstab but do not retrieve(*)

Place the composite report where you wanted the crosstab report. Pass on the arguments as appropriate but do not retrieve(*)

That's it. (All you need to do now is struggle with resizing and formatting)

Lars

(*) as the arguments appear to be passed but the preview window has been unaware since pb2. Save, close, reopen, double check arguments, THEN retrieve.

[Former Member]

Hi Franklin;

   Yes, a weird restriction IMHO. I would suggest submitting this as an enhancement request ...

http://my.isug.com/p/cm/ld?fid=187

Regards ... Chris

[Former Member]

Hi

What is the specific obstacle?

Are you unable to place a crosstab datawindow in the detail band of a tabular datawindow?

Difficulty passing arguments on from main report?

Lars

[Former Member]

Hi,

Sorry for my vague question.

Yes, I am unable to place a crosstab datawindow in the detail band of a tabular datawindow. The Crosstab would work on the retrieval arguments based on the values in tabular datawindow.

Thanks

[Former Member]

My Apologies, I have never tried it before and now get your original message about "Crosstab nested report with retrieval arguments can only be used in composites"

So the only workarounds I can think of is

• to make it a composite and retrieve it once for each and every master table row.
• to fake the crosstab report with painful retrieves or a sophisticated stored procedure. but as you say, the crosstab varies for every row.
• or have a datastore with the data to be cross tabbed and manually populate the nested "fake" crosstab report. Not that easy as the headers with need to be data too.

.

[Former Member]

Hi,

• to make it a composite and retrieve it once for each and every master table row.

     Re: Just to clarify the point : Using a getchild method, the nested report object would be connected and retrieved once for each and every master codes. Then how would it relate each other? Each crosstabbed data section would come under respective master code.

For e.g.

Code

1

     1.CrossTabbed data

2

     2.CrossTabbed data

3

     3.CrossTabbed data

and so on.....

• to fake the crosstab report with painful retrieves or a sophisticated stored procedure. but as you say, the crosstab varies for every row.
• or have a datastore with the data to be cross tabbed and manually populate the nested "fake" crosstab report. Not that easy as the headers with need to be data too.