We’re still in implementation and I’m testing out the creation of Stock Items through the APIs. Back when we had two segment Item Classes, I had no trouble creating Stock Items.
However, now that we’re testing out 5 level Item Classes, I’m having trouble finding the right ItemClass to send through the API. I keep getting “...cannot be found” on the Item Class object.
For example, here is a class from the Acumatica view: ONS.PIPE____.__REG___.________.___
I’ve tried passing multiple combinations of that class.
What is odd is when I query the stock item with that class, this is the output:
I’ve tried using that string as an input also.
Any help is greatly appreciated.
Best answer by jamest
@jamest,
With the SalesDemo data, I am able to set the multi-level item class, tested in 23.111.
Thinking, if it has to do with Acumatica version, can you please confirm the version you are using? Also, did you get a chance to test with a different multi-level value?
Ok, you pointed me in the right direction and got me thinking.
Here’s what I tested:
Does not work: ONS.PIPE____.__ASSY__.________.___
Does not work: ONS.PIPE____.__HEAT__.________.___
Works: ONS.FITTING_.ELBOW___.45DEG___.___
Works: ONS.FITTING_.________.________.___
Here’s my theory. If the segment is left justified to the separator it works. If there are spaces between the separator and object string it fails.
You can create the stock item with the class from UI or use an existing stock item with the class, do a GET request to identify the right format/value that you can use the in the PUT request. Good Luck.!
You can create the stock item with the class from UI or use an existing stock item with the class, do a GET request to identify the right format/value that you can use the in the PUT request. Good Luck.!
That’s what I tried to do. The screen shot is a GET of an existing stock item. I tried to reuse the Item Class value and it cannot find it.
With the SalesDemo data, I am able to set the multi-level item class, tested in 23.111.
Thinking, if it has to do with Acumatica version, can you please confirm the version you are using? Also, did you get a chance to test with a different multi-level value?
With the SalesDemo data, I am able to set the multi-level item class, tested in 23.111.
Thinking, if it has to do with Acumatica version, can you please confirm the version you are using? Also, did you get a chance to test with a different multi-level value?
Ok, you pointed me in the right direction and got me thinking.
Here’s what I tested:
Does not work: ONS.PIPE____.__ASSY__.________.___
Does not work: ONS.PIPE____.__HEAT__.________.___
Works: ONS.FITTING_.ELBOW___.45DEG___.___
Works: ONS.FITTING_.________.________.___
Here’s my theory. If the segment is left justified to the separator it works. If there are spaces between the separator and object string it fails.
