Dashboard Assembly Tracker with BAQCombo Fails To Filter

Epicor ERP 10
1

Epicor 10.0 Here!
We have a Dashboard that we created in Dashboard Developer (RunTime) with a Tracker for Filtering the results and one of the Filters need to be the Workforce/Sales Person of the Sales Order’s Customer, which is included in the Dashboard results as Customer.SalesPerson. But when we use the native combo created by the Tracker it displays ALL the Sales Persons and we only want to display the Sales Persons that actually have a Sales Order linked to a Customer. So to accomplish this we copied the Dashboard’s BAQ and adjusted it (with a subquery & Group By TopLevel query) to only include Sales Persons that actually exist on for Customes with Sales Orders… which brings the list down to 18, which is perfect. Then we customized the Tracker and added a BAQCombo for the Sales Person filter.

When we test in RunTime it works fine and filters as it should, but when we deploy as an Assembly that specific filter does not work and it returns all rows as if we didn’t select anything.
What’s the trick? Or is this a known bug of some sort?
Just seeing if anyone knows anything.
Thanks!

2

I should mention that I the Dashboard BAQ field name for the Sales Person matches the BAQCombo Value:

image
image707×236 42.8 KB

image

3

We always deploy as assembly, so I know BAQCombos can work :slight_smile: Though I tend to use Sales Rep filters matching the name rather than the code, since the name is actually displayed. (I doubt that’s the issue though)
I’d check to make sure the property for Dashboard Prompt is True (the default is false) That has always worked for us.

image
image846×196 66.9 KB

4

Thanks @MLamkin, but those settings are set properly as well. I probably should have screenshot the whole window.

5

this seems to be a quite old issue, but I was wondering if you found a way to solve it?

I’m currently struggling with the same issue in a 10.0.700.4 environment in which the assembly BAQCombo is not filtering, but the same BAQCombo in the runtime, works ok.

6

@Ruben_Corral_Yrureta
I don’t recall if this was resolved or not.
I think we just left it as a RunTime dashboard.
I think a further upgrade corrected this.