Kinetic UI, UBAQ based Grid on new slideout, baffled by SQL error

Kinetic ERP
1

Scenario:
I have created a new slider and added a couple of controls and a panel-card-grid.

Following the Application Studio guide and Hannah’s guide, I got it all wired up, and it seems pretty straightforward.

The odd thing is when I run my UBAQ in the BAQ designer it runs/updates just fine, but when my event runs and hits the erp-baq the payload looks correct, but the response is showing “Bad SQL Statement” (with no further details except a correlation id).

I made sure all the required and key fields specified in the Update Processing part of the UBAQ are both in my related view and the columns in the grid model of the grid

This is what my Network payload and response look like:

image
image817×311 11.9 KB

image
image757×457 7.86 KB

The actual where clause in the erp-baq/get/baq execute options is:
QuoteHed_QuoteNum = ??{TransView.OrderLineQuoteNum}

Removing the where clause results in the same behavior so I don’t believe that is the issue

Any ideas appreciated

1 Like
2

Are all your columns in the grid?

3

Yes, I just double-checked, all are present and all spelled correctly (then I use ‘Columns-Hidden’ to hide the ones I don’t want to show in the grid).

I’m hoping support can get me more info from the server logs about the error with the correlation id, that’s my only option if I’m cloud-Saas, correct ?

4

Open up server file download, choose the admin folder, and see if the server logs (appserverlogs) are listed.

If they are, open the latest one (most likely), and download that.

Should be able to find it in there.

If they aren’t there, probably have to contact cloud services to turn them on.

5

Also:

6

I had a similar error just today… BAQ ran fine, but my BAQ grid in my dashboard wouldn’t populate and I saw the same “Bad SQL statement”.

Luckily for me, it had been working and then I added some columns and started getting this error. The reason, I found, was I had a calculated field which, again, worked (or appeared to work fine) in BAQ designer… but one of the components was returning a null value.

Depending on your BAQ, I would review any potential pitfalls there and add some isnull() statements to your calculated fields.

This fixed it for me.

1 Like
7

@dcamlin Thanks for the idea, but unfortunately I have no calculated fields. I did have it working at one point but needed to add some fields to the ubaq…I also added them to the grid…it makes we wonder if it’s out of synch or something, like changes aren’t being recognized or properly persisted.

(I only think that cuz that’s the kind of issue i often see with Application Studio)

So still stumped, I may just start from scratch and see what happens

Also waiting to get access thru server logs via another support case

8

Found it…Got access to server logs :slight_smile:

Stupid typo on one of my columns QuoteHed.QuoteNum instead of QuoteHed_QuoteNum

Feeling like Homer Simpson

Scared Homer Simpson GIF by reactionseditor

3 Likes
9

But its working now!

Homer Simpson Skipping GIFs | Tenor

Homer Gif for every situation.

10

That’s me, everyday.