You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 13, 2021. It is now read-only.
When fetching entities linked to products via the API, the data returned for each linked entity seems to change unpredictably depending on what is passed in the "select" query parameter. I see this parameter is not included in the API docs (GET /Product/:entityId/:link), but is being used by GUI.
For example, the GUI is fetching product attributes by submitting a GET to /api/v1/Product/5cf9228ac7deb2492/productAttributeValues?primaryFilter=&select=attributeId%2CattributeName%2Cvalue%2CvalueEnUs%2CvalueDeDe%2Cscope%2CchannelsIds%2CchannelsNames%2Cdata&maxSize=200&offset=0&sortBy=id&asc=true
This returns a list of product attribute values similar to
Removing the "select" query parameter changes the returned items to look similar to below. Note that the values of the "isCustom" and "attributeType" fields have changed.
Hello, @jpars. Thanks for you feedback. When you remove "select" query parameter for product attributes returned data must contain all attribute fields. But now displays only "isCustom", "attributeType" and "productFamilyAttributeId" fields. There is a bug, that will be fix in version 3.2.4. If you add any values to "select" parameter, returned data will contain only this fields and also unique identifiers of attribute, attribute creator and assigned user. Invalid field names will be ignored.
When fetching entities linked to products via the API, the data returned for each linked entity seems to change unpredictably depending on what is passed in the "select" query parameter. I see this parameter is not included in the API docs (GET /Product/:entityId/:link), but is being used by GUI.
For example, the GUI is fetching product attributes by submitting a GET to
/api/v1/Product/5cf9228ac7deb2492/productAttributeValues?primaryFilter=&select=attributeId%2CattributeName%2Cvalue%2CvalueEnUs%2CvalueDeDe%2Cscope%2CchannelsIds%2CchannelsNames%2Cdata&maxSize=200&offset=0&sortBy=id&asc=true
This returns a list of product attribute values similar to
Removing the "select" query parameter changes the returned items to look similar to below. Note that the values of the "isCustom" and "attributeType" fields have changed.
Adding the "select" parameter with any value (even an invalid field name), changes the returned data of each item again:
I'm not sure how to interpret this behavior. If it is behaving as expected, could details of the "select" query parameter be added to the API docs?
Thanks!
The text was updated successfully, but these errors were encountered: