By using this website, you agree to our Terms of Use (click here)
Does anyone have experience and examples to share using the Contract Based REST API to get StockItem attribute values from an Acumatica instance? I’m able to retrieve StockItem data via the REST API but have not figured out how to get Attributes or their values.
This GET request works fine. It returns a 200 code and a nice json string with the expected data from our 2019R1 instance:
http://10.1.1.22/alive/entity/Default/17.200.001/StockItem?$filter=startswith(InventoryID ,'IDDG')&$top=5&$expand=Boxes
But when I try to retrieve attribute IDs or values from StockItems, Acumatica returns a 500 code without much to go on. I tried following the instructions in the Integration Development Guide but it isn’t real clear on this topic. I must have something wrong with the GET request syntax. Here I’m trying to get the value of the StockItem Attribute named A1007:
http://10.1.1.22/alive/entity/Default/17.200.001/StockItem?$expand=Attributes&$Custom=Document.AttributeA1007&$top=10
Made this request a few months ago.
If I remember right, you can not expand the Attributes only. you have expand all the fields include custom fields. that made the request very large.
or you can have another endpoint to request the attribute, and combine the data on somewhere else.
Thanks for your reply. It gave me a clue.
I did some more research and learned, if I’m understanding the documentation correctly, that you can’t expose attributes using a regular get request that returns multiple records. Attributes can only be exposed when retrieving one record by key. So to get the attributes for a stock item, I used two get requests, first to get the item id (which is different for each session) based on the InventoryCD and second using the id to get the item attributes.
Here's an example for the stock item IDDGLD08 that works:
#1 Get the item ID:
http://10.1.1.22/instance/entity/Default/17.200.001/StockItem?$select=InventoryID&$filter=InventoryID eq 'IDDGLD08'
This returns data that includes “836a2bb8-ed0e-4aa3-a582-388f90f99740” for the key.
#2 Get the item data including attributes using the id:
Alternatively, the oData interface can be used to get stock item data, including attributes, from a correctly constructed, exposed, generic inquiry.
Yes John, I built a GI and expose to OData. about 3-5s i can request about 4000 records.
much faster then restful API.
@programfred and @johnsp,
I think that OData also has the advantage of not being restricted by licensing limitations like API calls are as shown in this slide screenshot:
https://twitter.com/TimRodman/status/1204511100500414464
Online Members
