I remember telling my clients about a year ago that until Epicor really made some strides on Dashboards, that was probably the last major hurdle in getting away from Classic. I believe the 2025.1 and 2025.2 tools available with Dashboards have been some major improvements. I’ve gotten a lot of good information off this forum as well.
Yesterday, I watched Epicor’s Webinar on Dashboard Creation, and I probably came out of that with more questions. Which leads me to this post, with multiple ways of doing the same thing, I’m wondering how the power users here are doing it. The major questions I have:
- Are you going into Dashboard Maintenance, deploying the Dashboard to the Kinetic Application, then creating a layer on top of the DLL that Epicor creates? Or, are you going into Application Studio, creating a new App and using the wizards to create the grid views, do the publish/subscribe, etc.
- Most dashboards that I’ve implemented in Classic have had a Tracker panel which really was used for criteria entry. Date ranges, part numbers, part classes, etc were optional criteria. Are you using silent parameters and passing those to the BAQ’s? Or are you creating controls, binding them to TransView, and modifying the BAQ Options to use the TransView fields?
- I’ve had some discussions with my team (we are cloud), and we’re a bit concerned about our users not realizing they’re often seeing only the first 300 rows. We’ve discussed turning off the options that control that, so by default our dashboard ALWAYS return all the data. The main concern here is someone makes decisions based on the 300 rows they see because they didn’t know (or remember) to click the “more rows” option. If we do that, we’re likely going to implement some “hard” coded criteria in the BAQ (such as only showing last 2 years of shipments), and making some criteria required (have to enter a date range, for example). If users ever needed to go back further, we’d consider that an ad-hoc request and have to do it as a one-off. Wondering how you guys are handling this.
- When I used to deploy classic dashboards, I usually put the columns in what was the most logical order, and often sized the columns to make the dashboard more readable. With the Kinetic dashboards, the way I was doing this so every user wasn’t having to personalize their screen, was I was adding a width to the columns (dates at 90, for example). How are you guys handling this?
Thanks for the feedback!
