I tried just swapping the action out and it didn’t work. Kept complaining about not being able to find a erp-baq action. I have a bunch of testing ahead of me on this and am waiting for a response to development.
The really bad thing is we had to stop at 2024.1 on our last upgrade due to the issue with functions. Every dashboard we have converted so far is using the erp-baq widget and it’s looking like we have to rebuild all of them again for the next upgrade.
I know there are some tricks folks are using that pulls the JSON from XXXDef so they can use an editor to do global swap and use the BO method call to put the updated JSON back into XXXDef but I have not explored that. If anyone knows of a post that covers that, I would greatly appreciate getting a link.
Don’t think we got the Insights session collateral for that one yet.
As I recall, the poor mans way: If you trace AppStudio save post (Ice.BO.GenXDataSvc, I think), look in SysCharacter03(?) for the unpub version json
Exactly. It’s stored in SysCharacter03 and when published, gets moved to the Content field.
Erp baq widget still works in 2024.2. You dont have to replace it. In fact if you use data view guided setup the wizard will still create that widget in the get event.
Only thing that exposes the erp-baq widget error is when you manually add an event that calls it and then wire it to a button. Any of those layers that I have imported from 2024.1.x into 2024.2.x are throwing the same error. They all work fine in 2024.1.x. I have not yet tested in 2025.1.x.
You mean like event next on a button click?
I have an open ticket for this and several other issues I am running into when moving layers from 2024.1.x to 2024.2.x.
Dumb question, but are you sure it is a Date and not a DateTime?
There was an update in E10 that changed a table that used to hold a date to a datetime, even though the time portion wasn’t being set.
Our BAQs that looked for for a specif date weren’t returning anything. Turns out 11/24/2025 <> 11/24/2025 12:00:00
I have thought of the time stamp as well.
Turns out to be even weirder than I expected. In the BAQ, I am only returning the JobNum and OperSeq in my query results. I am not returning the ClockinDate because I don’t need to display it. The query works perfectly in the BAQ designer setting the @date and @oprseq. When doing the exact same thing using the erp-baq widget, I get no rows returned. If I delete the @date parameter which is set to ignore if empty in the BAQ it returns rows.
Just to grasp at anything, I added the ClockinDate to the query results and it worked. I can’t fathom why I would need to include the ClockinDate in the query results, the filtering should all be done server side and I don’t need to see it. This makes no sense at all. It has to be a bug in the release of Kinetic we are on now, 2024.1.21.
If I can make any better sense of what is actually causing this or if I confirm it’s a bug in this release, I will update.
I’ve seen issues like that before… Kinetic is weird.
Turns out I am not the first one to report the issue with the erp-baq action not up lifting properly. Problem case PRB0298849 has been linked to existing cases related to this.
