Home End User
New Blog Posts: Merging Reports - Part 1 and Part 2

Crosstab i EU

edited April 2004 in End User
In your previous posts...
When you create the first DataView in the data workspace, it
atomatically attaches the data pipeline for that dataview to the report.

This means that the report will traverse the data.

When you create a crosstab in the detail band of the report and assign
it to the same pipeline, this sets up a situation where both the
crosstab and report are traversing the data.

This creates a 'repeating' crosstab effect.

The answer is to manually disconnect the report from the data pipeline
(via the Report | Data menu option) or to move the crosstab to a
non-repeating band, such as the title band or summary band....

...

I try both in EU but here are my problems:

In solution "manually disconnect the report" when I remove it ... then I
cannot assign data in my crosstab (report is empty)?

In second way I cannot make multiple columns (in a case that Crosstab is
narrow to fit twice on page)

Is there any help?

THX!

Benjamin

Comments

  • edited April 2004
    OK now I get it...but maybe for some other users....

    1) manually disconnect the report (via the Report | Data menu option)
    2) move crosstab to detail band
    3) select crosstab
    4) from combo (Data Pipeline names) (in left upper corner) choose
    datapipeline which will Crosstab use.

    It was tricky...but just to tell you that many of us have allready made
    start templates for reports so modificiation for regular crosstab
    setting was (at least for me!) not so easy...

    ;-)

    Ben

  • edited April 2004
    OK now I get it...but maybe for some other users....

    1) manually disconnect the report (via the Report | Data menu option)
    2) move crosstab to detail band
    3) select crosstab
    4) from combo (Data Pipeline names) (in left upper corner) choose
    datapipeline which will Crosstab use.

    It was tricky...but just to tell you that many of us have allready made
    start templates for reports so modificiation for regular crosstab
    setting was (at least for me!) not so easy...but now is OK!!!!!

    ;-)

    Ben

  • edited April 2004

    Simplest way to create a crosstab is to use the Crosstab Report Wizard - it
    configures the datapipeline connection for you.

    --
    Nard Moseley
    Digital Metaphors
    http://www.digital-metaphors.com


    Best regards,

    Nard Moseley
    Digital Metaphors
    www.digital-metaphors.com
  • edited April 2004
    Hi!

    This is true...but in acertain way you have a bug. How to create it?
    1) Click on Crosstab (with an report that have defined pipeline)
    2) define from the menu that report has no data (pipeline)
    3) look in combo which shows data for crosstab-it still shows pipeline.
    4) now save the report and that settings has no effect-crosstab has
    still defined datapipeline!!!

    Combo is updated when you move focus...but this is obvious what the
    problem is.
    ;-)

    Hope this could be fixed in next release...maybe it is not so important
    but i think is easy to fix.

    Ben
  • edited April 2004

    I tried some tests. The only issue I could find is that the
    ParentDataPipeline property is should be published for TppCrosstab, as it is
    for TppDBText.

    For any data-aware component, if the ParentDataPipeline property is True,
    then modifications to the Report.DataPipeline property are propogated to the
    data-aware component and its DataPipeline property is updated accordingly.
    However, if ParentDataPipeline is False and you modify Report.DataPipeline,
    the change is ignored by the data aware component.

    You can see this by placing a TppDBText component on the report and toggling
    its ParentDataPipeline propery. This propert is not currently published for
    TppCrosstab, but it should be. We can fix this for the next release.


    --
    Nard Moseley
    Digital Metaphors
    http://www.digital-metaphors.com

    Best regards,

    Nard Moseley
    Digital Metaphors
    www.digital-metaphors.com
This discussion has been closed.