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
Slumber instead seems to be escaping the quotes, so the url that I've tried does not work. api.PricingProductPrice.get(_where='Product.id='FBBE591D76204756A4E349FEF6E41D6D'')
The request sent by slumber to the webserver is this: org.openbravo.service.json.jsonrest/PricingProductPrice/?_where=Product.id%3D%27FBBE591D76204756A4E349FEF6E41D6D%27
while the correct one is this: org.openbravo.service.json.jsonrest/PricingProductPrice/?_where=product.id='FBBE591D76204756A4E349FEF6E41D6D'
Do you think that such particular use cases could be supported by slumber? More examples of such queries are available on the openbravo website:
I'm trying to use slumber with the openbravo erp json api, which has some kind of inline query system within the query string.
The url is something like:
https://hostname/org.openbravo.service.json.jsonrest/PricingProductPrice/?_where=product.id='FBBE591D76204756A4E349FEF6E41D6D'
I've been able to call it using requests with the following parameters:
requests.get('https://hostname/org.openbravo.service.json.jsonrest/PricingProductPrice/?_where=product.id=\'FBBE591D76204756A4E349FEF6E41D6D\'')
Slumber instead seems to be escaping the quotes, so the url that I've tried does not work.
api.PricingProductPrice.get(_where='Product.id='FBBE591D76204756A4E349FEF6E41D6D'')
The request sent by slumber to the webserver is this:
org.openbravo.service.json.jsonrest/PricingProductPrice/?_where=Product.id%3D%27FBBE591D76204756A4E349FEF6E41D6D%27
while the correct one is this:
org.openbravo.service.json.jsonrest/PricingProductPrice/?_where=product.id='FBBE591D76204756A4E349FEF6E41D6D'
Do you think that such particular use cases could be supported by slumber? More examples of such queries are available on the openbravo website:
Thanks a lot for this powerful tool.
The text was updated successfully, but these errors were encountered: