I have a trail of rest service calls I have that start a clock, start an active labordtl, GetNewLaborDtlOnSelectForWork, and then I run and update, I am setting the part for the detail in the object, which has been working, but with a recent update, I keep getting error about “An Attribute set must be specified.” I’m not seeing a clear trace that helps address what’s going on or how to pass the data through another method that builds the object correctly
Did you implement AUOM, start using attribute sets, or potentially inventory by revision? It sounds like it is looking for an attribute set for your part.
we are doing inventory by revision, and it’s definitely looking for an attribute set for the part. I’ve written an automated service external to Epicor that’s creating expense entries that won’t succeed because of it. I am happy to add an attribute set to the part in rest as well, but I’m not familiar with it and I’m not seeing where to go to trace a process for it. The expense in Epicor works fine, and I don’t see a trace of anything happening that’s related to the attribute set
Attributes are a new feature and it just mean they changed the signature of the methods to take in a potential attribute you just have to pass a blank one
1 Like
I appreciate what you’re saying. I can’t see where to pass a blank one though or where to control through the laborSvc process for capturing the entry through rest.
I figured it out thanks. I don’t know if my local version doesn’t exactly have the module, or what the story is, but there is just very slight differences between one environment and the other. The AttributeSetID was not present in my local environment even though Dynamic Attribute sets are still there. It’s a little infuriating to be honest. 
1 Like