Hello! I’m finally digging into placing Panel Card Grids into some of our tracker screens. I created this one in Part Tracker. I created the data view and followed the instructions with the where clause Part_PartNum=?{KeyFields.PartNum}. It worked!
Except… when there’s a part that’s a replacement part, it pulls in correctly with just one line item (as it should). But when I pull up a manufactured or finished unit it pulls in the entire list from the BAQ. There are no filters or conditions on the BAQ that should cause this. Any ideas?
When I filter the BAQ to that part, it only pulls in one line, but in the PCG on Part Tracker it pulls in the whole list. I’m stumped. I’ve started from scratch on the BAQ and PCG but it still does it.
What is the event that triggers the BAQ data to load?
Is the KeyField.PartNum field reading correctly in Part Tracker?
I suspect that something is happening when you change the part in PartTracker, it’s reloading the grid before the KeyField.PartNum is set. You can check what KeyField.PartNum says by using the debug tool.
Great question. I don’t know. When I set up the data view this “event” was created through that process. Should I set a trigger to see if that fixes is? Sorry… I’m new to these events in application studio.
Thank you. Now it pulls the whole BAQ list for all parts and freezes the system. I can filter the BAQ to eliminate manufactured parts; this is really just for our parts department anyway. I just figured I’d try. Thank you!
OK now it’s back to pulling the whole BAQ results list for every part. It seems to work fine without the new event but it acts like the where clause doesn’t apply for certain parts. Would that even make sense?
