BAQ Combo customization - how to convert from Classic to Kinetic

I have a Classic BAQ Combo customization on our MES Start Rework Activity menu and I am trying to convert this to Kinetic using Application Studio. The BAQ combo displays available DMR #'s based on the Job Num, Assembly, Operation entered/selected on the MES Rework Activity.

I can get the DMR # field to display on the kinetic menu but it is grayed out and I cannot figure out which setups in Application Studio to populate to trigger the BAQ which in classic returned the list to be displayed in the drop down.

I have tried adding EpBinding & EpBinind Text Column in the Data section
And populated the Advanced section

Has anyone figured out how to do this yet?

Make sure to populate the TextField property.

I must be missing something else or entering something wrong as I added the Textfield and still doesn’t work.

Here is what my Classic Customization looks like…

The BAQ used for this is as follows:
[DMRHead].[DMRNum] as [DMRHead_DMRNum]
from Erp.DMRHead as DMRHead
where (DMRHead.OpenDMR = 1 and DMRHead.JobNum = ‘[Like:JobHead.JobNum]’ and DMRHead.AssemblySeq = [Like:JobAsmbl.AssemblySeq] and DMRHead.OprSeq = [Like:JobOper.OprSeq])
group by [DMRHead].[DMRNum]
order by DMRHead.DMRNum

Did you try removing this? You shouldn’t need it.


As an afterthought–if you go to the DataViews section on the far left of App Studio, do you see the “Start” DataView?

No I do not see “Start” - is this something I need to add as for the Classic customization I did not add this that I recall.

They may have changed the view that is being used.
What are the other fields on the screen bound to?

Other fields are bound to KeyFields and LaborDtl. I tried both and get a little farther in that the DMR # is no longer grayed out but when I select it I get “No Data Found” . Wondering if now something needs to change in the BAQ?

Try this in the browser:
Preview your layer.
Press F12 to open Dev Tools.
Drop down your BAQ combo box.
Go to the network tab of the Dev Tools and look for an Execute By ID (or something similar).
Click on that event–does it give you any clues?

Additionally, when you run the BAQ in the BAQ editor, it pulls back data, yeah?

Looking at your query, it looks like you’re filtering on Job/Asm/Op–are you doing that in the BAQ? Via parameters? In App Studio?

It’s the BAQ as for the Classic customization I use the where (DMRHead.OpenDMR = 1 and DMRHead.JobNum = ‘[Like:JobHead.JobNum]’ and DMRHead.AssemblySeq = [Like:JobAsmbl.AssemblySeq] and DMRHead.OprSeq = [Like:JobOper.OprSeq] and the drop down list only returns the open DMR #'s for the Job/Asm/Op I entered/selected on the Start Rework Activity screen

So, what I would do is remove this stuff from the BAQ:

‘[Like:JobHead.JobNum]’ and DMRHead.AssemblySeq = [Like:JobAsmbl.AssemblySeq] and DMRHead.OprSeq = [Like:JobOper.OprSeq]

Then add those to the where clause in App Studio to filter the results based on the fields KeyFields.JobNum, LaborDtl.AssemblySeq, and LaborDtl.OperSeq.

Do you have any examples of writing the Where Clause as I tried several combination that were in various post but nothing seems to be working

So, looking back at my notes, it turns out the where clause is bugged.
There are a couple methods you can go from here.
You can set up the filters/filtersParams.





(No spaces in these lines)

One thing to note about the bold items in this line: QuoteNumCol=?[QuoteNum],QuoteLineCol=?[QuoteLine] is that the combo only knows about the fields within the dataview its bound to. In my example, the combo is bound to QuoteDtl.Character01, so it will only know about fields within the QuoteDtl table. This is why you only need to write it as [QuoteNum] vs [QuoteDtl.QuoteNum]. That being said, it’s also a limitation if you need filters from multiple views. If you do, then I suggest following the below method and bind them to a BAQ View.


You can create a BAQ View to load your data, then hook into an action (like AfterGetByID) to create an event to filter your view based on the loaded Job/Asm/Op, which is a bit more complex.

Here are some snips of the BAQ View version.

Another edit–you could also probably use the REST widget to call your BAQ and populate the filters or parameters that way and then plop that into a view and bind that view to your combo.