The network call should show you the problem.
I have seen this issue as well. I think itās related to multi-company.
I usually switch to another company and then back again. If that doesnāt work, I then click the URL and delete everything after āā¦Apps/ERP/Homeā and then refresh the pageā¦this usually works.
Nope, because the slide-out is intercepting whatever is happening, and thatās what shows up in the network call.
The console log will show your baq get event firing. If it doesnāt show yourevent firing, that means you still have it configured for provider model.
It does show it firing, yes. But before it shows up there, the slide-out parameter panel triggers, and itās what is entered there or not that is in the event request data.
That indicates you are still set up for provider model.
Youād think so, but itās the same whether thereās anything entered in the provider model settings or not. Possibly thereās some cache problem or something not cleared at some level, though, possibly.
But the problem showed up in existing dashboards after the upgrade that had never had the provider model settings.
Yeah its probably that. Makes sense with how buggy the new screens are and especially around multi company.
I made a uBAQ for a company, and then added custom code to it. But the code portion got registered under a different company than the baq was for so when I went back to edit it later, it was really goofy to try and get access to both parts.
OK, this is bizarre and a bug, but I have finally found what the bug is, and why it hasnāt happened more commonly to anyone:
It turns out that the culprit is an updatable field in the BAQ thatās set to have a dropdown with reference to another BAQ. For some reason, that BAQ reference confuses the dashboard and it appears to mix the parameters and execution settings for the original BAQ and the referenced one. So making the updateable field a standard open-input text fixes the problem.
well.. itās a bandaid. Those drop downs are essential to a lot of processes because bad data is ā¦ BAD. And free text leads to a lot of bad data.
Thatās me mad at Epicor^^
This sounds similar to a couple of other bugs, it confuses lower level subquery fields with top level subquery fields and the provider model puts the sort columns in the select clause.
Definitely seeing a lot of the same hiccups as othersā¦BPM code failing to execute, right now we canāt enter orders or ship in Pilot. Most base items and some BPMs seem to be OK. Found what appears to be a base error in Customer Shipment Entry (showing all sites and not just the active one for the user) and thereās a case open.
No worries. Itās only day 3. Weāve got a month to iron it all out before it goes live.
Thanks Jill!
Which pisses me off to no end. An app of any kind, grid, whatever has ZERO reason to know anything about the structure of fields from anything below the toplevel query. NONE!
Fortunately it doesnāt stop there being a dropdown in the interface, only in the BAQ itself. But it does seem ridiculous as a problem.
Production Upgrades for ANZ/Germany/India/UAE are this weekend - Be interesting to get a REAL summary of how that goesā¦
Jaysusā¦None of this means a thing right nowā¦
Re: the date thing.
In Scotland we use Day, Month, Year spoken as well as written.
i.e. āI was born on the Twentyfirst of Jan, 1970ā (not really) or āMy date of birth is 21/01/70ā.
Find the correlation ID then look for the BPM thatās throwing the error. Or you can skip that log step if you already know which BPM is the culprit.