We are in fairly early days of implementation. I’m in the process of mapping out REST API calls to create a sales order and its line items in an external configurator. So far it’s going pretty well! The tricky thing I’ve run into is line item attributes (this is how we store our part number colors). As far as I can tell, attributes are assigned at the line item release level, and any attempts I’ve made to assign an attribute to a line item at its creation has resulted in an additional release that contains the attributes, rather than “release 1”.
Problem:
I figured I’ll just create a UBAQ that I can call to update a line item releases OrderRel_AttributeSetID after my initial REST POST creates the order. Well… I’ve run into this:
Can anyone think of a way around this? I’ve kind of been voluntold into an ERP Analyst position and I’m crash coursing my way through all things Epicor, so fairly new!
As far as I can tell, attributes are assigned at the line item release level
Haven’t worked with the attributes myself, but your answer probably lies here. The attributes are assigned/associated to the release, but probably not defined/entered there. So you are poking in the wrong BO
Apparently the trace tool is called the Debug Tool these days. I had turned it on just to check it out before but I didn’t try actually doing anything with it on so its usage slid right off my smooth brain. Also didn’t make the connection that I could just turn on the dev console in the browser version and look at the payloads for the API calls being made. Whoopsie.
For future googlers unfortunate enough to find this thread, the endpoint that sets attributes in an orders line item release: Erp.BO.DynAttrValueSetSvc/UpdateAttributeValuesObject
I’ll keep experimenting with this but you guys set me on the right path, thanks again !
