My custom POForm report style has an error when batch printing. If it is used to print a PO individually, all is well. When used to print a batch, some of the POs are printing with the following fields sometimes incorrect:
-PO Numbers (sometimes jump to next PO # on pages after first page of PO)
-Order Date (sometimes blank on pages after first page of PO)
The last batch was 45 pages and included 29 Purchase Orders. All look good until page 14, where on page 2 of the PO, the PO number changes. (It’s supposed to be 23661 but it shows 23662.) Then after that, PO numbers are incorrect on many pages (after the first page) on each PO.
Must be something with the grouping, right, but I can’t find it and I’m afraid I’m making it worse. Can anyone point me in the right direction? In the meantime, my Purchasing Dept is having to print these individually, which is not ideal.
I just ran with the Std SSRS and the PO Numbers are all correct. I re-ran with my custom report and again, all are good until the 4th PO (pg 11), where the number changes on page 2 and the OrderDate is blank on page 2. I’m going to deep dive into the rdl. It’s got to be a little box somewhere with code messing something up, or something incorrectly set. This used to work! I’m going to find it. If you think of anything else, please update.
UPDATE**** I re-ran a mass print with the same PO’s and the report printed with the same exact errors, so it’s not random.
The only thing I can think of doing is to allow the group to break. In other words, make sure that on the PONum group it doesn’t have “Keep Together” checked.
The PONum variable that is displayed on the top of the header is re-set each new PO group. On page two there is no group change, but for some reason it is changing.
It is odd that the standard report works, but yours doesn’t.
I think you can open an RDL in notepad++ if I am not mistaken? You could try to do a compare on both files to see what has changed.
I can’t quite find what is causing the issue, but the fact that the base works correctly is a sign that you may need to step back a bit and try to re-assess the customized form. I think it would have to do with grouping, but I don’t know how custom code executes when it is put in groups. I barely know how it works anyways.
