Two report questions

A problem has been identified with a clients Customer Statements and Invoices. 

Most of the reports are 1-2 pages but occasionally there are 3 or more page invoices and statements. 

Three page statements are pulling header info for the next sequential customer in the batch while displaying the report content of the third page. 

This shifts the whole thing off and the rest of the reports are wrong. 

We can reproduce it every time an invoice or statement in a batch is 3 or more pages. 

Any insight on how to troubleshoot or where to look next would be much appreciated. 

I think the data being pulled incorrectly (the header and totals on the bottom) is using the Get\Set logic in visual studio where as the data that works (body of the report) uses the default style '=First(Fields!VAR_Message.Value, "DataSet_Result")'

Have you experienced this with a report before? 

Do reports need to use one or the other method to stay consistent? 



The second question is related to the micr line on the check report object. Clients are printing and seeing the line in various places on the report moving vertically up and down. I tested and saved to pdf and found that the line is moving there too so the printer is not responsible. what could cause it to move like this. I even uploaded an old object that didn't have this problem and the textbox control is still moving around. It's interesting that nothing else on the report moves as the batch prints just this one text box. 

Any resources or good lessons on RDLC NAV development I should be checking out? 

  • for these two Questions, may I have your codes?
    idk I have some experiences before!
  • Hi Rob,
    If you are completely new to NAV RDLC development, then I suggest that you check out some of the many video's on this, that you can find on YouTube. Just search "dynamics nav report designer". Here you will also quickly learn that the reports we in NAV refer to as "document reports" are much more complex, than "normal" RDLC reports.

    The document reports have build in handling of multiple copies and pages and non-standard changing headers. They can be very difficult for a "newbie" to debug or just explain, but for the trained report developer, looking at the source code he may easily spot the issue. Which is why Maihuishin asked for this.

    If the report has been customized from a standard report, then try to run the un-modified version to see if you have the same issue with the standard report. If not, then you need to compare the code to see why not.
Related