Text box parameters not loading in data

I’ve got parameters that are not loading in their data. When testing the BAQ itself in Run Query, the data populates. In Application Studio, I’ve connected the text boxes to the EpBinding data view, and I’ve implemented an event that should call the BAQ and DataView and populate the parameters with the data after the TranID is picked. I have a feeling they are not populating because I set up the event wrong, but I am worried the error may be coming from somewhere else. Does anyone have any thoughts on this?


Are you familiar with the debugger in the browser?

Can you see your event firing and your BAQ being called? (If no, could be a trigger issue).
Can you see data in your BAQ dataview afterwards? (if no, could be an issue with your kinetic-baq event action).

1 Like

Thanks for the suggestion, I haven’t checked the debugger yet. I just checked it and ran it again and confirmed the BAQ is executing, so it probably has something to do with the kinetic-baq event action, or maybe a misspelt DataView binding somewhere.

If you want to plop your kinetic-baq settings in here we can help take a look.


i’ve got nothing under execute options or behavior

In your field value in your BAQ Parameters, try wrapping that in curly braces:

{NonConf.TranID}

Tried and no luck. This is my BAQ, very simple one table with some criteria.

I have a feeling the error lies somewhere here or still somewhere within the event that’s restricting it from putting the data into the text box parameters, maybe not restricting but missing information somewhere.

I generally avoid using parameters (if I can) because they end up being a headache in Kinetic/App Studio events.

If it is a simple BAQ, I would try deleting the parameter on the BAQ… then in App Studio, in your kinetic-BAQ action, I will go into the “BAQ Execute Options” and add a where clause like: UD08_Key1 = '{NonConf.TranID}'

This should run your BAQ passing a “Where” statement instead of a parameter.

If your BAQ is complex and you use that parameter through multiple subqueries, etc. then, that may not be an option… but since yours is pretty simple, a where clause may be easier to pull off.

Thank you for the tips, I appreciate your time. I tried doing that but no luck so far, but I think I will stick with using the where statement rather than the parameter, your reasoning makes good sense. I’ll be doing a lot of trial and error and I’ll reply when I get it working.

plop GIF

1 Like