Hey folks!
Your friendly, neighborhood Kineticist here with another episode of “How To Kinetic”!
Today, we’re going to talk about how to publish and subscribe two grids of data in Kinetic!
I’ll be using two BAQs, but the principles should remain the same for subscribing to a native grid.
Let’s get started!
Go to Properties > Grid Model > Provider Model > Baq Options. This is where you can fill out a where clause to filter your results. I have set mine to filter my results based on the Quote Number of the loaded form. If you have multiple filters, you can use the ‘Where List’ section instead.
Place a new ‘Panel Card Grid’ on your design surface for BAQ #2.
Go to Properties > Grid Model > Provider Model and enter the ID of your second BAQ in the ‘Baq ID’ property. (You can also take the time to edit the columns in Properties > Grid Model > Columns at this point).
Go to Properties > Grid Model > Provider Model > BAQ Options to fill out the where clause. I used a Where List for this example, so you may see how it’s configured.
Column: This is the column from BAQ2 you wish to filter on. Make sure you use the full column name from the BAQ (IE, OrderHed_OrderNum). Condition: Condition to filter by. I set mine to equals or ‘=’. Value: This is going to be the value from BAQ1 in the format of ‘??{DataView.FieldName}’. Recall that I named my DataView “RelatedOrders”. The two ‘??’ means we can pass a null value back.
That’s it! Save and Preview your layer and you should see your grids working!
I was attempting to replicate this in the issue material entry app but I was not able to filter on the KeyField. (JobNum) I can give the where clause a direct value and it will filter the dataview accordingly but when I try to use the above syntax to filter on the KeyField it just returns all rows from my baq. Any idea what I may be missing here?
I created a new layer from base to follow along with your changes and it still doesn’t want to filter. Could it be a version issue with Kinetic? I’m currently on 2021.1.11
It would seem that the whereclause doesn’t allow the ‘-’ (hyphen) character that is prevalent in our job numbers. I verified that this was the case by selecting some jobs without the hyphens and they filtered correctly. Not sure if this is intended or how to get around it since it seems to be on the KeyField entry.
