I added a BAQ dataview to the PO entry module. It has the part number, part description, and a UD field I created for specialized data on the Part table. I am trying to add an event to populate the table so that I can pull the specialized info into a text box on the PO Line Details screen. The data will not populate. I’ve looked at other posts here, but I haven’t really seen one that has helped me. Is there somewhere I can find good instructions on how to do this? Could there be a post I’m not seeing?
What is the event trigger and are the trigger conditions being satisfied?
Post a screen shot of the event as well. That will help folks give you some pointers.
I’ve pulled additional information into the PODetail screen, if this is helpful to you. The tricky part is that there are multiple ways to get to the PODetail screen and different events that fire if the PartNum on the PODetail form changes… so you may (will) need multiple events to cover the various scenarios.
For example, in my case, wanted to see the Part’s drawing number (PartRev.DrawNum) on the PODetail form (assuming the part had a revision and the revision had a drawing number assigned.
So, I added the textbox to the form (set to Read-Only).
This is bound to PartRevAdd.DrawNum… getting to results from my added PartRevAdd dataview:
So, I need a “master event” with no trigger.
Event Actions (yours may vary):
- I clear the PartRevAdd dataview
- Condition
"{PODetail.PartNum}"===""(Checking to see if PartNum is empty.) If FALSE: - Condition
"{PODetail.RevisionNum}"===""(Checking to see if RevisionNum is empty.) If FALSE: - Perform my rest call to populate my PartRevAdd dataview.
In your case, instead of a rest call, you’ll be performing your Kinetic-BAQ (or rest-baq depending on your version).
My rest Method Parameter is where I tell the call to use the PODetail.PartNum as the key value I want returned:
I’m not going to paste all my settings for this rest call as you’re doing this via BAQ call. But… if you need help with settings here, just paste what you have and we can help troubleshoot.
That should do it for your “master event”. Now we need to create additional events for WHEN we want THIS event to fire.
I found I needed (4):
-
If you’re already on a Line Item record and the user changes the PartNum
-
Any time the RowChanged_sysPages event runs… if the PartNum is defined run my event
Condition: "{PODetail.PartNum}"==="undefined"
-
If the user clicks a Line Item number in the POHeader form (Line Grid)… it navigates to the PODetail form… I need my event to run. So, I trigger this one after the native event:
-
If you’re on the PODetail page and use the top navigation to go to a different line… run my event:
Hopefully that covers all the bases.
David, thank you for this. I will definitely try this out.
I would assume yes. In BAQ Execute Options, you would want something like…
Where:
Part_PartNum = '?{PODetail.PartNum}'
The Part_PartNum would be whatever your BAQ PartNum column is.
… another thought though, looking at that screen shot. The View Name of PODetail may not be right. You’re not adding to the PODetail native dataview. You want whatever BAQ Dataview name you created to go there.
When you run the BAQ, it will pull data back into whatever DV name you enter there. Then your textbox on your form would have a matching binding to that BAQ dataview to display the value.