Customization field of BAQ Report in Menu maintenance

Hello everyone,

I have created my first BAQ Report and would like to create a menu. But, after selecting BAQ Report in the Menu Maintenance, nothing appears in the Customization field.
Every other BAQ report I’ve seen has seen it appear here.
Why doesn’t this field appear? Is there something I’m missing?
Thanks in advance!

You have to create and save a customization in Developer mode before you will see it in the customization list there. You also have to close/restart Epicor to see the updated change to the menu.

Sorry to bother you, but this is my first time creating a BAQ Report…
I entered Developer Mode and opened BAQ Report Designer.
What should I do next? All I had to do on the dashboard was Action > Deploy, but I don’t know how to do BAQ Report.


Hi,
It is not necessary that you need a Custmization for a BAQ report, If you are generating the report with default report options and filters, you can leave the empty.

Thanks,
Arun

I am trying my hand at creating a BAQ report for the first time. So I don’t know much about it.
What is the “generating” task you mentioned?
Why doesn’t anything appear in the Customization field in Menu maintenance?

If you are new, I recommend beginning with a User Guide or a YouTube tutorial for a better understanding of how things work. Customization dropdown will display the customization layers, if you have any and it will be empty as it is a new report.

1 Like

What @iarunkumark is trying to say is that your report should run fine without a customization. It’s only when you enter your report menu item in developer mode and make changes to it, then save the customization, you will be able to find it in that list. However, for your purposes, as far as I know you will not need a customization.

1 Like

You are almost there. As others have said, you probably don’t need a customization. Lets start from the beginning:

  1. You write a BAQ to return some data from Epicor. This BAQ will feed your BAQ Report.

  2. You create a new BAQ Report that contains the BAQ, a report format, and optionally some Filters, Sorts, or Option Fields. If your BAQ from the step above already returns the data you want, then don’t setup any filters or anything at the BAQ Report level.

  3. Now you have to create the BAQ Report format. Actions > Download SSRS Report. Choose Desktop to download the blank report template to. This template has your datasource calls built in, but not the actual data.

  4. Navigate to Desktop\Reports\CustomReports\ and open the rdl file you just downloaded. This should open in Microsoft SQL Server Report Builder 3.0. This is where you build the actual report and put in the fields, grids, or whatever you want to show. Save the rdl file to the same location and go back to Epicor > BAQ Report Designer >Actions > Upload SSRS Report. Choose your desktop as the source, and it will automatically find the reports\customreports\ folder. This is a sticking point for some people. Make sure to always use the same folder for download and upload.

  5. Now you have a BAQ that gives you the data you want, and a report format that should display it the way you want. before deploying it to the menu, lets test it out. BAQ Report Designer > Actions > Preview Classic Form. Test your report here until it runs perfectly. Edit and reupload the report format until you get it right.

  6. Once you have it right, and you want to deploy the BAQ report to the menu, go to Menu Maintenance and add the item just as you did. You don’t have a customization yet, so don’t choose one. Just select everything else just like you did. Save, and close epicor. Reopen epicor and navigate to the menu location where you added your report. you should see it there. If you do not, then you do not have sufficient permissions, or there is another issue.

Regarding Customizations. You would apply customizations to your dashboards, not to BAQ reports. Generally speaking you don’t need to use customizations with BAQ reports. Customizations can be used to create your own forms with text boxes, buttons, grids, etc. Don’t go down that rabbit hole unless you really need to.

1 Like

Great! Thank you very much for your detailed explanation. I understood that BAQ Report does not require Customization.
But, a report error occurred, so I mistakenly thought this error was due to customization. When running the Preview Classic Form in BAQ Report Designer, the error below popped up. This has been well tested at BAQ. I just set up some Option Fields and Filters in BAQ Report Designer.




Do you have any parameters for your BAQ? You cannot use parameters with a BAQ report. Instead, you just setup the BAQ to return all the data, and then use the BAQ Report tools (Options, Filters, sorts) to modify the output to the actual report. I suspect you have parameters mucking things up.

My BAQ has no parameters. However, it has a Constant value in Table criteria.
Should I not set table criteria as well?


If you go in Developer mode and Preview Classic Form, do you see your customization? Or maybe go into the deployed menu in Developer mode if you see the customization there also.

Contant values are ok, as are just about any other criteria.

1 Like