Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 264 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 385 SQL Performance
- 33 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
Report Header issue
c_smith
Member Posts: 8
Hello everyone,
We just made the jump to NAV 2015 after having been on 3.7 to that point. We brought over all of the customization that was in the old system, which of course required quite a bit of work on Reports (among other things). Hopefully I can articulate clearly enough the issue we've come across.
Where we are having the issue is with the printing Purchase Order batches (as well as other batches). We set up the Header/Footers of the purchase order to use the GetData/SetData functionality, and at first it seemed to be working as expected. The header/footer info was matching up with the given body info, etc. But yesterday we discovered that whenever there was a purchase order that extended onto a second page, the Header/Footer info would move on to the next PO number, while the body was still displaying the remainder of the previous POs lines. And the header section remains ahead of the body section from that point forward in the batch. The end result being mismatched Header/Footer and bodies.
Also of note is that if you print a multi-page PO by itself, it works as it should.
I'm sure I'm missing a setting on the report that would keep the Header/Footer matched up with the body, but I can't find it to save my life.
Any advice?
We just made the jump to NAV 2015 after having been on 3.7 to that point. We brought over all of the customization that was in the old system, which of course required quite a bit of work on Reports (among other things). Hopefully I can articulate clearly enough the issue we've come across.
Where we are having the issue is with the printing Purchase Order batches (as well as other batches). We set up the Header/Footers of the purchase order to use the GetData/SetData functionality, and at first it seemed to be working as expected. The header/footer info was matching up with the given body info, etc. But yesterday we discovered that whenever there was a purchase order that extended onto a second page, the Header/Footer info would move on to the next PO number, while the body was still displaying the remainder of the previous POs lines. And the header section remains ahead of the body section from that point forward in the batch. The end result being mismatched Header/Footer and bodies.
Also of note is that if you print a multi-page PO by itself, it works as it should.
I'm sure I'm missing a setting on the report that would keep the Header/Footer matched up with the body, but I can't find it to save my life.
Any advice?
0
Comments
Please confirm about below points -
1. Are you using SetData and GetData as per Standard of NAV 2015?
(In earlier version we used to have Red Text Box in header for GetData, which is no Longer Required).
(In earlier version we used to put the Header Fields in Hidden TextBox/Table in Expression, which we put now in Visibility).
2. Is your TextBox / Table that have header information is within a List in the Body or Not?
3. What is the Grouping & page Break in the List if it exist?
Do let me know the answers, i will try my best to help you out.
Thanks & Regards,
Saurav Dhyani
Do you Know this About NAV?
Connect - Twitter | Facebook | Google + | YouTube
Follow - Blog | Facebook Page | Google + Page
did you know, that you cannot delete a post, which you have erroneously posted?
..., I tried it, but ... no way.
If you place your SetData in a Table in the body the part where your SetData is should be rendered on every page. Also you should have a look in Report 206. Look at the List element behind the table. And check the grouping.
Check out this Report ...
https://onedrive.live.com/redir?resid=8F46B6AC358F1DCE!37493&authkey=!AOhuqnFMzRwSnq0&ithint=file%2ctxt
Try to delete the Page Break Option inside the Group. The last item from the dataset of the currentPage will be "Set" with the SetData Option.
With kind regards
mik