I’m needing to add an additional Filter Option (new Tab) value and a Sort By (added to the combobox list) option to the OpenPOReport system report. I understand this is a system report that comes out of the box with Epicor.
The value to be added to both the Filter and Sort By is the Buyer value. These look to be added to the OpenPOReportForm where different criteria can be selected that controls the report output. ….if it can be done.
I do know enough about adding a new Buyer Tab to the criteria form. The real issue would be to understand how to pass that value to the system report.
I did see one posting that said to ‘duplicate’ the existing report and add what I need to the customization. If that is the way to go, then can the system report be duplicated? If so, how? Then there’s the issue of connecting and passing values to the report.
I hope this doesn’t mean I have to start from scratch … I see there are a couple posts here that are similar to what I’m asking with no responses. Does this mean it’s not possible?
Do you need the ability to select multiple buyers? If not, you could add a retriever combo to the form to select the buyer. Then bind that to callcontext variable, and pass that to the report. In the report’s RDL, add a filter to hide records of buyers that don’t match the callcontext value.
This is actually a two part project; 1) Allow the report to be Grouped by Buyers, and 2) Allow for the selection a Buyer.
So, are you indicating this is possible? The reason I state it that way is because this is a system (old Crystal) report and the BAQ used for this isn’t available. I can see some things within the RDD for this report, but not a whole lot.
I’m very interested in the binding you’ve mentioned and how to hide records.
When you say “old crystal report”, you just mean it’s the one Epicor supplies? (which is actually a SSRS report).
Or is it really a crystal report? To be sure, go to Report Style Maint and check the Report Type for the style you’re using.
You should copy the report style (select the style to duplicate, then Actions -> Copy Report Style on the menubar). Then you can make changes to the newly created RDL, without affecting the original.
In the new RDL, add a grouping on the Buyer. And it will always group by the Buyers regardless of which sort style is selected. If you want to make that grouping optional, you could add a checkbox to the form, and pass its value via a callcontext variable.
Looking at the Report Style Maintenance, I do see the Standard style is an SSRS, however, there are 3 additional style definitions that are of Report Type Crystal. This is because this system I’m working on was recently converted from E9 to E10 and they were using Crystal Reports in E9. These were not converted to SSRS before converting to E10. So … I’ve been told to disregard the Crystal reports and only focus on the Standard report for right now.
Copying the report style sounds easy enough, but I would like to see the Sort By field include a Buyer option as well as having the ability to Filter By Buyer as well.
I’d like to have a better understanding of what you mean my “pass its value via callcontext variable.” Obviously, I understand that a value is being passed to the report as a criteria. But, by copying the Report Style, does that include the OpenPOReportForm where these options can be selected?
Launch Report Style Maintenance, and load the report ID
Copy the Report Style to a new Style
Download the Report
Open the report you downloaded with Report Builder
Edit the main dataset’s query expression. Adding the field to the select phrase, and a new join phrase. In my example (the OpenPO report), the PoHeader dataset is the main one. So in its query expression, I add the highlighted parts:
Now I can use that checkbox’s value in my report. For example, to enable a grouping
Save the Report RDL
Upload to server (via Report Style Maint.)
Notes
You can add a control on the form to use as a filter, but it only affects the rendered output. It does not filter the data created by the RDD. So make sure that you use it appropriately.
Our preliminary testing shows this works! My boss, Jim McCoy, who is also posted on here was able to pass a text box value using the steps listed here. We really appreciate it!
