Tracker filters don't work on assembly dashboards in 2022.2?

Kinetic ERP
1

When using a combo to filter in the tracker view on a dashboard, it filters as expected in runtime but seems to ignore the filter when deployed as assembly. I see an Epicor KB article that says to just use BAQ parameters instead. That’s not really a solution as the BAQ parameter functionality is really annoying (constantly pops up). Plus we have a lot of different filters and they are all optional, so having them in the tracker view is ideal.

I see several old threads on this issue but not any alternative solutions. I’m confused why this isn’t considered a bug and been fixed by now (we’re on 2022.2)? Curious if people have found other workarounds or solutions?

These dashboards are still in classic. I am considering rebuilding them in kinetic to see if that solves the problem but that is a long term solution not a quick fix.

2

I don’t have this problem. Must be very specific.
I have whole applications built on this functionality.

3

Yeah its not all filters that aren’t working, just some. Not sure why. Here is an example of one that doesn’t work in assembly:

image
image530×630 14.2 KB

4

So what does happen? What’s the KB?

Is that a combo you made, or one of the epimagic ones?

5

image
image771×611 19.5 KB

6

These dashboards predate me so I don’t know how they were created. I guess I could just try recreating the epicombos and see what happens, haven’t tried that yet.

7

I have this same problem. I opened a case with Epicor and they were not able to solve it for me. It seems to me that it’s a bug. Also, it’s not specific to combo boxes, it also has this same problem with some text boxes for me. The strange thing for me is that in the dashboard menu when creating the dashboard, the filters work. But as soon as you create the dashboard assembly the filters no longer affect the query results.

I’m hopeful that there will be a fix or patch for this as it does not seem to have an obvious cause or solution.

8

Are they custom tracker controls or the “epimagic” kind as @klincecum puts it.

9

I was able to solve this on ours by just deleting the fields and recreating them. I can’t explain it. Maybe some kind of corruption? Ours were custom controls.

2 Likes
10

@aosemwengie1 - I just tried to do some tests and it seems that the only fix is to create a new dashboard from scratch. I made an identical dashboard, but I had to start from scratch and now the filters are working.

Here are a few thing I tried before building the dashboard again from scratch.

  • Make a calculated field that is equal to the broken filter, then point the dashboard filter to this new query field (This didn’t work)
  • Create a new top level on the BAQ to see if the query results are somehow causing the Dashboard filter issue (This didn’t work)
  • Export the Dashboard and BAQs then try and make a copy of it to see if the dashboard filters are working properly in the Copy of the Dashboard (this didn’t work).

Thanks.