Hey guys, super new Epicor user here (~1 month) so please forgive me if I am not using the correct terminology. And I am using the classic screens still (we are just about to upgrade to the browser-based ones)
I am trying to make an updateable dashboard with three publisher baqs and one main updatable subscriber baq. I have everything working except I want to know if it is possible to turn off a publisher baq to just filter with one or two of the other ones.
While this is relatively straightforward in classic, and I understand the urge to just get it done, I would highly suggest you just bite the bullet and do this in app studio. You’re just creating technical debt for yourself, and you will hate yourself for it.
Take the opportunity. The rest of us learned the hard way, there is no reason you should have to.
Unfortunately, I don’t know if we have the correct test environment setup for the browser screens for this project yet. What you are saying is a dashboard like this would have to be recreated once we finalize the upgrade?
If you are on a release version that has Kinetic options, you should not need a test environment. You should be able to create the dashboard in Application Studio using the same BAQ.
Sooo is the solution to my problem in App Studio the same as in the classic screens? I am going to try and build both honestly because I need the practice in classic for right now and I’ll need the practice for App Studio once we fully get there. I still don’t know how I would go about doing this filtering issue…
To answer your original question (and not the philosophical one of which system to use), I do not know of a way to turn on and off publish and subscribe on the dashboards. It’s either on or off.
I’m sure there is a way to code around the issue, but it’s not going to be any easy setting out of the box.
I have a dashboard with this requirement. I created a card stack. The first page of the stack has the publish/subscribe parent and child grids. The second page of the stack has the child data again, but in a separate dataview and grid so it doesn’t filter off the parent grid.
Right yeah, I thought of maybe just creating different tabs for which filters you would want to use I was just hoping there would be a better less clunky solution then that.
Thanks a lot Kevin I am going to try out this solution. This is what I was thinking if we could have a null option to select it might work and I think you figured it out.
