mibuso.com
Home› NAV Three Tier

RDLC Headerinformation on second page

mschuemschue Member Posts: 8
edited 2013-07-26 in NAV Three Tier
I have a problem in MSVS.

If i add headerinformation with ReportItems!<...>.value it is only visable on the first page of a report. On the following pages there is no data anymore.
If I use the function SetData(ReportItems!<...>.value and GetData(...) I get information on the following pages.

The question is: Does ReportItems!... not affect pages different from the first one?

(View Screenshot for more details)

Thanks in advance.

*edit*
Some more information:
- All Fields in the Header section have parent property "Page Header"
- I can put the red (invisable) fields from the body also on the List object which includes grouping. This does not affect my problem at all.

Comments

  • BeliasBelias Member Posts: 2,998
    "reportitems" gets the value form the textboxes currently displayed (even if hidden, obviously) of the report (for example your red textboxes).
    The problem is that your textboxes would have been printed only on the first page, because they're not in a table, thus they are "out of scope" when printing the second page.
    You can try to move a pair of "red" values in the body sections of the table object to try it out
    -Mirko-
    "Never memorize what you can easily find in a book".....Or Mibuso
    My Blog
  • mschuemschue Member Posts: 8
    Thanks for the help.

    The "red" fields are already in a tableobject in the body section. They are only printed in a textfield in the header section. But this should have no effect in the visability since I have textboxes in the header, which are visable on all pages.
    I don't know why they should be "out of scope".
  • BeliasBelias Member Posts: 2,998
    from what i can see from your screenshot, the red fields are NOT in the table drawn below...you have to move them in the body of the table of the rdlc layout.
    -Mirko-
    "Never memorize what you can easily find in a book".....Or Mibuso
    My Blog
  • mschuemschue Member Posts: 8
    I tried that already (the screenshot is older, when i tested something).

    In the ss below you see that the red fields are in a body-tablerow and they are all on the list object where the grouping is defined.
    Still on the second page i get no data.
  • BeliasBelias Member Posts: 2,998
    try to make the red fields visible, and see if they actually prints on all the pages. (i guess they does print only on the first one).
    I think you're printing a 2-pages invoice. This means that the repeating item is the second table, where you do have the lines. If so, you've to move the red textboxes in THAT body item. Here's what happens now:
    1. your "red table" prints all his textboxes before start printing the detail table you have below
    2. the detail table starts printing and it continues to the second page
    3. the second page starts printing the remaining part of the detail table (the red table have already been printed before, thus you don't have the values in the second page)
    4. the group finishes and a new invoice starts printing
    -Mirko-
    "Never memorize what you can easily find in a book".....Or Mibuso
    My Blog
  • mschuemschue Member Posts: 8
    Sounds logical. I'm going to try that. I already tried to make the red fields visable (this has no effect on the reportitems).
  • BeliasBelias Member Posts: 2,998
    mschue wrote:
    I already tried to make the red fields visable (this has no effect on the reportitems).
    surely it doesn't have effect: the only purpose of making them visible is to make you understand that they're not printed in the second page (thus, they're "out of scope").
    let me know the result :!:
    -Mirko-
    "Never memorize what you can easily find in a book".....Or Mibuso
    My Blog
  • mschuemschue Member Posts: 8
    Hm did not work somehow. When I put them in the row of the maintable some fields are not printed on the first, some not on the second page.

    Had not enough time to test it all. I'll make an other test with a feedback in the afternoon. Thanks for the help!
  • BeliasBelias Member Posts: 2,998
    you have to check what values are not printed, because they're probably not evaluated at that point in the dataset...it all depends on the dataitems/sections design in classic client.
    -Mirko-
    "Never memorize what you can easily find in a book".....Or Mibuso
    My Blog
  • mschuemschue Member Posts: 8
    SOLVED:
    Ok I had 2 problems mainly:
    1. PageSize (width) was too large (second page was created automatically) so that the value in the body field was not sent to the header (via ReportItems).
    2. I needed to put the fields which are being shown on the second page into the headerrow of the maintable which is printed on every page. (As you mentioned)

    Thanks for the help!

    Now I have an other Problem (I'm awaiting an MS incident).
    If i put headerinformation hidden (on the second page) the space is not released. Is there a way solve that?
    My idea: Put it in the body section into a tablerow and put this visable/hidden depending on the page. (this is not a good way in my opinion)
  • BeliasBelias Member Posts: 2,998
    If i put headerinformation hidden (on the second page) the space is not released. Is there a way solve that?
    it's a known issue: no feasible solution so far...
    -Mirko-
    "Never memorize what you can easily find in a book".....Or Mibuso
    My Blog
  • mschuemschue Member Posts: 8
    Ok thanks for the help. I'll post a solution if I got answer from MS.
  • chj124chj124 Member Posts: 1
    the solution is simple... to keep the header from being a fixed lenght which happens when you use a rectangle...

    ditch the rectangle, insert additional rows (however many needed) and set the visibility on the row, this will allow you ro reclaim the space if noting is valid for that row
Sign In or Register to comment.