UBAQ Failing In Kinetic

I have a UBAQ dashboard that I had deployed with Application Studio. It was working well until this week. Now the updateable part of the BAQ doesn’t seem to work. It uses a custom action to process the updates. The data is going into my callcontext fields like it should, but nothing is working on my UBAQ side.

Setting the application aside for a moment, I just open the UBAQ, and try to manually enter a record. Normally I can do this, if I type in all the right values it expects, but not anymore. I have removed all the widgets from the BPM, and replaced them with just a messagebox to show debug info. With start linked to the messagebox only.

Does anyone know of any issues that could be causing this sudden change? I just get that cryptic error 500 with no details. :thinking:

polyfills.fed6889ba0feb400.js:17 POST https://REDACTED/api/v2/odata/VTAERO/Ice.BO.KineticErpSvc/UpdateBaqCustomAction 500 (Internal Server Error)
main.4040f515affc62a1.js:523 erp-rest-service [post] 500 - Internal Server Error Http failure response for https://REDACTED/api/v2/odata/VTAERO/Ice.BO.KineticErpSvc/UpdateBaqCustomAction: 500 Internal Server Error; “We apologize, but an unexpected internal problem occurred. Please provide your System Admin or Technical Support this Correlation ID for further details. Correlation ID: e71995bf-03f5-4f5b-afb5-31cfd17fe8b5”
error @ main.4040f515affc62a1.js:523
ERROR {“headers”:{“normalizedNames”:{},“lazyUpdate”:null},“status”:500,“statusText”:“Internal Server Error”,“url”:“https://REDACTED/api/v2/odata/VTAERO/Ice.BO.KineticErpSvc/UpdateBaqCustomAction",“ok”:false,“name”:“HttpErrorResponse”,“message”:"Http failure response for https://REDACTED/api/v2/odata/VTAERO/Ice.BO.KineticErpSvc/UpdateBaqCustomAction: 500 Internal Server Error”,“error”:“We apologize, but an unexpected internal problem occurred. Please provide your System Admin or Technical Support this Correlation ID for further details. Correlation ID: e71995bf-03f5-4f5b-afb5-31cfd17fe8b5”}

2 Likes

Have you downloaded the server log to get the data from the correlation ID?

2 Likes

I am on cloud. I went to Server File Download, but I don’t see any files that relate to the issue. I couldn’t find any files there that had a recent date, so I think I dont have access to that.

1 Like

You checked the admin folder I assume.

3 Likes

You’ll want to go into the Admin \ Log folder, pull the latest log file (or the right one within range) and search for the string.

My Dev Tools dashboard has a log file search that you can plonk the correlation ID in, and it will take you straight to it. (on cloud)

3 Likes

We’re on cloud - select Admin from the dropdown, then look for the appserverlogs folder. Can take a few seconds for the folder to appear but then you should be able to search/download the appropriate file.

EDIT - or use @GabeFranco 's dash, probably a lot easier lol

3 Likes

They should be in as @GabeFranco said under Admin appserverlogs folder. I agree Gabe’s tool is easier than the method Epicor forces on us.

2 Likes

Unless you are on government cloud. Still no log file access there.

4 Likes

I had a few UBAQs which suddenly stopped working on some update and it turned out the Query to Object column mapping & Object to Query column mappings didn’t match up. Could be something similar here?
For me, it was a date field which was being parsed as System.DateTime which needed to be System.DateTime? (but only kinetic would fuss about the field being nullable)

4 Likes

Did you report that? How exactly fields did not match?

2 Likes

Oh, I forgot about that problem, you are right, that has happened to me with more than one uBAQ before. I had to click the “Resync column mapping” button or whatever it was. Same thing, DateTime vs. DateTime?

3 Likes

I have reported it. Per support, the solution is to reselect the service method. They don’t see any reason to report it to development and do not know the root cause.

6 Likes

So what are steps?

2 Likes

Reselect the service method in the ubaq. That’s it. Then it works.

3 Likes

no, I mean how exactly it did not work? what was set in the UBAQ initially?

2 Likes

In my case, I had OrderHed.OrderDate mapped to . . . . OrderHed.OrderDate. Worked fine in classic, failed in kinetic.

4 Likes

You mean if you create BAQ in classic and then open in Kinetic?

2 Likes

The BAQ was created who knows when in Classic. Maybe E10.

3 Likes

I thought this might be the case as well, but my UBAQ uses advanced BPM processing rather than the standard update BPM. I have been suspecting that date/time thing as the issue. I hate tried various ways to make the field formats match, with no luck. Where can I add that ? to the end of the DateTime?

3 Likes

An Epicor employee saw this post and reached out to offer me a snippet of the log that I can’t access. This seems to be the relevant part, something about a messed up JSON in queryResultDataset. Unexpected end when reading JSON. Path ‘queryResultDataset’

{"Source":"EventLog","LogEntry":{"EventSource":"IceAppServer","Time":"2026-01-19T17:44:26.0000000Z","Channel":"Epicor App Server","Level":"Error","EventId":0,"Message":"Ice.Common.EpicorServerException: Unexpected end when reading JSON. Path 'queryResultDataset'.\r\n ---> Newtonsoft.Json.JsonSerializationException: Unexpected end when reading JSON. Path 'queryResultDataset'.\r\n  
 at Newtonsoft.Json.Converters.DataTableConverter.CreateRow(JsonReader reader, DataTable dt, JsonSerializer serializer)\r\n  
 at Newtonsoft.Json.Converters.DataSetConverter.ReadJson(JsonReader reader, Type objectType, Object existingValue, JsonSerializer serializer)\r\n  
 at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.DeserializeConvertable(JsonConverter converter, JsonReader reader, Type objectType, Object existingValue)\r\n  
yaddah yaddah...

Dev tools only shows me the error I first posted. Kinetic UX Trace doesn’t see any BOs fire off to trace. Where could I poke around to find that JSON? I still have my BPM kneecapped, from Start right to a single debug text box showing the variables pulled from callcontext fields. That dialog box never fires either. So, I dont think the UBAQ even gets to the action part.

3 Likes