Updatable Query PartPlant.VendorNum

[Nancy_Hoyt]

Good Morning,

I am driven bonkers by this updatable query. Can someone throw some ideas about how to do a workaround to get this working as needed/expected? I have simple UBAQ below, it’s for PartPlant vendor number update. See screenshots. System claims its doing update but does not do it. How can I force the VendorNum change into the field as needed? I’ve messed with BPMs within the UBAQ a little here and there and I wonder if there’s a way to do this. I suspect it’s a bug in my version…

Thanks for any ideas,
Nancy

PartPlantUpdate.baq (23.1 KB)

[ckrusen (Calvin Krusen)]

No exact answer for you, but some things to think about…

A trace of manually changing the Vendor on the Part-> Site sheet reveals:

(I think this was the call made when I typed in the new VendID, and it looks up the Vendor info)

and this is the actual update.

Note that it includes a column name VendorNumVendorID Which is what DMT would use…

[ckrusen (Calvin Krusen)]

Hmmm … If I add the column PartPlant.UrgentVendorNum and make it updatable, it can update the Urgent Vendor field on the Part->Site.

Processing update on:

yields

[Nancy_Hoyt]

I get the same Calvin. Also SLTVendorNum is updatable like normal. It’s the VendorNum that’s driving me nuts.

And there is no VendorNumVendorID in the part plant table. Also, I looked at it in SQL server, not there either “hidden” from BAQ somehow.

[ckrusen (Calvin Krusen)]

I’ve:

1. Added the Vendor table

2. A calc column named VendorNumVendorID (which is just the VendorID)

3. Made Calculated_VendorNumVendorID updatable

4. Added a row to the output mappings:
   

   

And that saves and runs with no errors, but still doesn’t update PartPlant.VendorNum

I’ve even tried setting both PartPlant.VendorNum and the VendorNumVendorID fields to see if that would then update but still no luck.

Also tried just updating PartPlant.VendorNumVendorID with VendorNum being un-updatable. Still fails.

[Nancy_Hoyt]

I ran the trace on the updatable BAQ for when the VendorNum update fails VS the SLTVendorNum is successful. The darn thing, they are both the same from what I see.

[ckrusen (Calvin Krusen)]

If I make the target Column a bogus name like PartPlant.VendorNumVendorIDX

I get an error while saving.

Problems in BAQ update processing
Output mapping expression for ‘ttResult.Calculated_VendorNumVendorID’ field is invalid: ‘PartPlantRow’ does not contain a definition for ‘VendorNumVendorIDX’ and no extension method ‘VendorNumVendorIDX’ accepting a first argument of type ‘PartPlantRow’ could be found (are you missing a using directive or an assembly reference?)

So the fact that it does save ok when the field PartPlant.VendorNumVendorID is used, must mean that is valid.

edit

If I launch the Expression editor for the output fields, I see all the pseudo-fields from the trace in my first post.

Perhaps they need to be set as well. Or maybe just the RowMod field needs updating