Dear Team
Good Morning.
After the recent version upgrade to 2026.100.6, updateable dashboards are not working. Do we have any alternate options available?
1 Like
Weāve seen the same issue. Only option weāve found is to rebuild the dashboards moving away from uBAQs to Functions.
Since itās dashboards & BAQs support will reject a ticket unless there is enough proof. Epicor broke something but I donāt know what with enough detail yet to submit a ticket. Feel like a catch-22.
If its working in live and broken in Pilot and the only thing that changed is the upgrade, that is enough proof to submit a ticket. Just package from both environments and submit it to them.
Steps to reproduce: Upgrade
Weāll find out what they do.
Can you share the specifics of the issues with updateable dashboards, do they not load at all or issues with filters/parameters? Our updateable dashboards with UBAQs seem to be working in Pilot 2026.100.5. We are on-cadence and are scheduled tor 2026.100.7 in Pilot July 7-8 so little time to test that version before it is applied to Production.
Ok ticket number is CS0005535325
There is now an open PRB0319252 for UBAQ dashboards not working in 2026.100.6. We are on-cadence 2026.100.5 and that is the version we have been testing. There is an upgrade to 2026.100.7 scheduled for 2 days before Production Live. There are planned fixes in 2026.100.7 inc Quote worksheet calc, but new things such as broken UBAQ dashboards leaves us with only 2 days to test before Production. In testing - hopefully fixed before Production live.
PRB0319252 PD State In TestingReproduction steps:
-
Create a simple uBAQ
-
Create an updatable dashboard. Use the uBAQ as the datasource.
-
Test the dashboard. Update a field. Click on āUpdateā. The error with the correlation ID shows up.
We were seeing the issue in .5 though soā¦ 
Our case is tied to that PRB too.
is there any examples that any one wants to share a function on doing updates to baqs?
Iāve had to get several dashboards working again, and mainly they needed the update functionality re-adding in the uBAQ (for some reason the upgrade stripped it out in each case), plus a different way to add the RowMod back in the dashboard itself.
Worth checking if either or both those problems are behind you problems before rebuilding around functions just to get data updated.
There are other deeper problems with dashboards passing the wrong data to uBAQs recently, but for most simple dashboards the above are what Iād check first.
For two of our dashboards we have custom BPM methods to update the data and it wasnāt stripped out. We have a simple one that uses the stock BO and it too was still there in the BAQ side.
Yes, āAdvancedā wasnāt stripped out, although it was disabled.
But the standard updates were all gone.
At appears, from what Iāve seen, too, that thereās a problem with conditionals using āEnabled by directiveā in custom work on BAQs. But I didnāt have time to find out why or whether it would be fixed, just moved everything to custom actions instead.
Interesting. Iāll have to go look at our 3rd to as itās untouched. Maybe I missed it.
Agreed, something is wrong with 26.100 with updatable dashboards either on the uBAQ or App Studio side (or both?)
I think it may be both, but I donāt have any dashboards that are created through the wizard process so the App Studio side for mine may simply be that theyāve invalidated assumptions Iāve depended on. Apart from the muddled parameter issue, which is definitely a bug.
I had got into the habit of updating RowMod on uBAQ rows using an event triggered by columns changing. But it seems as though changing the same row that just changed now doesnāt work. So Iāve done the RowMod work on the save event itself, which feels less elegant but more reliable.
I do wonder if thereās a change there thatās affected things more widely, since fixing it solved the problem for me.
Weāre still seeing Dashboard issues in 2026.100.7 with BAQ Where List filters. 
Us as well. This isnāt good.
Too bad Epicor is only delaying the upgrade for customers they have decided have EFCore issues, when there are so many other issues that are just as critical, and those customers have no option to delay unless they pay an exorbitant fee of $26,400 for extended flex plus a database downgrade fee of $5,000. Why would we want to downgrade pilot when the whole point is to have more time to fix the issues, not less.
26K for a one time flex?!
