Found @Randy’s post about it here: It's here.... 2026.1.100 Feedback Thread (Behave 🤣 ) - #138 by Randy but was hoping to open up a new thread singled in on this issue. I’ve found a few dashboard grids that were working fine on Friday, but unfortunately are now dead in the water. I believe I use the Provider Model to load all of my dashboards so hoping there is some resolution on this.
With one of the grids, I cannot even get it to execute the BAQ (like somebody had mentioned). Really have no clue what is going on there. Within that same dashboard though, I have a grid that will execute the BAQ, but not return anything. In the DevTools, it just says “Bad SQL statement. \r\nReview the server event logs for details”. However, if I pull that BAQ up in the designer, it runs perfectly fine (no errors or even warnings).
I’ve also got a couple of grids in that dashboard that will run fine. So far I have only found this on 2 dashboards, although I fear I will run into this as I check more of them. I spent most of the day cleaning up BPMs…
I do have a case open (CS0005554510), but I will update this case with anything that I find. Hopefully others will be able to share some solutions on this as well!
I saw an inconsistency in Pilot vs Live on one updatable dashboard that was working fine in Pilot but not in Live. Spent many hours getting it to work since it is a critical dashboard. The App Studio and BAQ were brought into Live from Pilot thru Solution Workbench. In Live, the add new row was failing (not happening) sometimes (not always) and also the BPM Data-directives that set the unique keys failed sometimes but not always. I recreated the dashboard in Live in App Studio using the wizard as I am still learning App Studio. The add new rows is working now but sometimes have to refresh to get that to work. The data directive is now working since modifying the pre-process method directive. I will continue to work on copies to try to resolve the issue with the add new row sometimes requiring F5 refresh. So far, the other dashboards are working in Live as they were in Pilot. Hope you don’t run into many more dashboard issues!
In more interesting news: I’ve found another BAQ that we use in 4 separate dashboards. It will load data in 2 of them just fine, but in the others I get 2 seemingly different behaviors. In on of them, which oddly enough is the dashboard where that is the only grid, it will say “Loading records” and show the spinning icon, but will never return anything. In the other one, I get the “No records available” and it doesn’t even look like it’s trying to load anything. Neither of the bad ones show up in the DevTools as even attempting to execute the BAQ.
Update: Regarding the BAQ mentioned above, I got one of them to (kind of) work by removing the views I had on the grid and revert it to using the Grid Model → Provider Model. However, as soon as I added BAQ Options, it failed to load like in @Randy’s post (full circle). Might be able to use this on some dashboards where they were bricked, but I will update my ticket to give Epicor more information. Really must be the BAQ Options since one of the dashboards using the same BAQ doesn’t have any Views.
Who knows if it is at all related or not… but I found one simple baq dashboard today that wouldn’t load data… it actually WAS running the BAQ event, just wasn’t displaying anything. I found if I collapsed and re-expanded the grid, the data would appear.
We had similar issues with a couple of dashboards when testing 2026.1 in our Pilot system about two months ago**.** What we found is that the dashboard would fail to load when opened up, the blue status bar would zip across real fast but no data loaded. If you refreshed the grid after that it usually worked. The BAQ behind worked just fine. We submitted a case which turned into a PRB (PRB0318105**).**
I had a couple issues like this today, one of them being the slide-out on get-details in engineering workbench was showing up blank, and also the same issue as this post. Both were fixed by right clicking in the blank area and clicking reload frame. I did this after cleaning all the application data/cache for the related computer, but that might not be required for the fix.
