To make it more interesting, I don’t know what table name to pull the cost from as there is a naming discrepancy, cost. in the cost adjustment module and costpart in BAQ design.
I always found it frustrating how many different ways you could go about doing the same thing… usually unclear to what makes the most sense. A BAQ Dataview might be a good fit for this if you’re just looking up standard cost to display it. There should be examples on here for that. I’m not sure if you’ll find the adapter you’re looking for in the FKV to pull in the cost record associated to that part. But if it’s there, you’re halfway there.
I’m not familiar with that, FKV were my only tool, and it’s a dull one at that. I’ll do a little more digging to see if I can find some guides on baq dataviews.
Here’s something to confuse you more… I’m pretty sure the result of a ZoneBAQ is yet another dataview in the background . The first time I heard of a zone BAQ was from @Rich at insights like 7+ years ago and they were cool. Do you have access to documentation @rirish ?
Then in Part Entry and open a part and right-click on the Part# and select “More Info” from the list. It’ll run your BAQ and show the data. Here is an example of one we have in Order Entry for Part# info:
They are a under appreciated and not often spoke of but powerful tool for certain needs.
We only had one in Classic and now we have multiple for this reason too. I liked how Classic’s version was just a mouse-hover in the field “tick mark” to trigger the ZoneBAQ over Kinetic’s click-fest to be honest…
Utah, good question…I thought I had covered most of the scenarios, but changing parts on a new po line after the price is pulled in is not working yet. Back to the drawing board, thanks for helping my poke holes in this thing!
Edit: That one looks to be solved! I’ll update the code block above.
And that’s what I was trying to get at, we still have to account for all the events that would cause the dataview that it’s joined to to change, right? I wish that it changed and inherited the same base events as the one it was joined to.
The original code only ran the BAQ on grid row activation, so changing partnums on the same row didn’t trigger. We added a refresh trigger on partnum change to remedy.