I’m working on a customization for job traveler and noticed that the operation details are getting split between pages. The report is the exact same as the default ssrs report with a few additional fields added.
Requirement
What I want is to have the operations start at the top of a page, run through however many pages are required to show all the details, and then decide whether there is enough room for the next operation to fit on the same page or move it to the start of the next page.
Additional Information
In the past, I have simply put a page break between each operation to force it to the top of the next page. However, this causes a lot of wasted paper/whitespace on the traveler.
That question is hard to answer in any detailed manner. It all depends on the stance of the company on custom reports.
I see people choose to use BAQ reports, SSRS reports that use SQL connections, customized report styles using a base report data definition, customized report styles using a customized report data definition… there are many options.
We had to re-build a report that replaced the job traveler because the company was going a different route with the way they wanted the info laid out and the order in which they wanted jobs printed…
My rule of thumb is to stay within the framework of Epicor reporting. Use built in reports that have report data definitions and customize them as needed. If that doesn’t work for one reason or another and you have to build out a report with a direct sql connection then do it as you need, but that is not recommended.
In short, if the logic is already built out and the out-of-the box report has all the data you need, start fresh with a blank report, but use their report data definition.
