Using orderEditBegin is giving me a null calculatedOrder id. Reference: https://help.shopify.com/en/api/guides/editing-orders#begin-order-editing
By doing this query in POSTMAN:
mutation beginEdit{ orderEditBegin(id: "gid://shopify/Order/<ORDER ID>"){ calculatedOrder{ id } } }
Result:
{ "data": { "orderEditBegin": { "calculatedOrder": null } }, }
URL: https://shop_name.myshopify.com/admin/api/unstable/graphql.json
Headers
X-Shopify-Access-Token: Private App Password Content-Type: application/json
Hi @JaypeeGaran,
Are you attempting this mutation on a developer preview shop? Currently the only way to test Order Editing is using the unstable version on a Developer Preview.
See https://developers.shopify.com/changelog/edit-orders-with-our-new-order-editing-apis for more information.
Best Regards,
Ryan
Hi,
I'm having this issue on a production store with the 2020-01 api version. According to the guide: https://help.shopify.com/en/api/guides/editing-orders
I'm still receiving null for the CalculatedOrder.
Am I doing something wrong?
Puda
Hello @Ryan,
I am able to edit an order using graphql if I create the order manually in the admin page for a development store I am using to build an order editing process I want to apply to my actual store. However, when I try to edit an order that i have created using graphql, I get "calculatedOrder": null in the response. In addition, i cannot edit the order manually if I create the initial order in graphql. So the problem seems to be with orders created by graphql. There are no obvious issues actually creating the order with graphql btw - everything looks fine (item, price, shipping, etc.) when I do this and then check the order in the development store.
My app has permissions to edit orders, and indeed it does this just fine if I create the order manually. Is there some setting or configuration that I am potentially missing from the order creation process that permits it to be edited?
User | Count |
---|---|
12 | |
12 | |
10 | |
8 | |
7 |