I have a Kinetic application with two UBAQs on it inside grid panels. The UBAQ custom actions work fine in pilot, but after I deployed to live, I get that standard server side error:
We apologize, but an unexpected internal problem occurred. Please provide your System Admin or Technical Support this Correlation ID for further details.
Since this worked well in Pilot Kinetic (2025.2.7), I assumed it would work fine in Live Kinetic (2025.2.7).
Does the correlation ID in AppServer Log give any useful detail?
Doe it ever? Seriously though, I am on cloud and I think I have to make a blood offering to support to get that kind of detail.
With SSRS, no, almost never!
But with BAQs i’ve usually found a tidbit of good info when referencing the correlation ID, such as a null reference in a calculated field that only strikes at row 10001 of the result set, so works fine in baq designer but bails on a dashboard. Seems that the BAQ Exception handling is a little more robust at returning a useful error.
(On 2024.2) I found a couple weeks ago that my uBAQ freaked out when I tried to add a UD field to the display fields.
That is, in the browser I failed. In classic it worked. And then the app was fine in App Studio also.
Maybe the UD part is irrelevant and just any field would have failed.
Are we supposed to report these things?
This doesn’t relate to your specific issue; just the title.