Deprecated call message calling orders end point

[rplum]

I am making this call:

/admin/api/2022-01/orders.json?limit=100&status=any&updated_at_min=2022-02-01T19:40:47.0000000Z

and getting a deprecated call notice in the response header.:

X-Shopify-API-Deprecated-Reason
https://shopify.dev/changelog/property-deprecations-in-the-rest-admin-api-order-resource

(this is a dead link)

I get this response only when making this call for stores that have mutli- locations enabled.

the same request to a different Shopify store, with only one location enabled

/admin/api/2022-01/orders/count.json?status=any&updated_at_min=2022-02-01T19:57:05.0000000Z

gets no deprecated call header.

When I check the deprecated calls resource for the stores that are getting the deprecated call header, I see this sort of response:

"api_type": "REST",
"description": "The fulfillment_service_handle property will no longer exist on the FulfillmentOrder resource.",
"documentation_url": "https://shopify.dev/api/admin/rest/reference/shipping-and-fulfillment/fulfillmentorder#properties-20...",
"endpoint": "Fulfillment Order",
"last_call_at": "2022-02-01T18:57:23.000000Z",
"migration_deadline": "2022-04-01T15:00:00.000000Z",
"graphql_schema_name": null,
"version": "2021-07"

the deprecated call response is on the orders end point NOT the fulfilment orders endpoint as the response says.

I do call the fulfillment orders end point like this:

/admin/api/2022-01/orders/(orderID)/fulfillment_orders.json

and this call has no deprecated call notice in the header.

the mentioned property -- fulfillment_service_handle -- is not used, and I see no reference to it in my code.  I am not even finding it in the json response from the orders call that is triggering the deprecated notice.

I am at a loss how to proceed to remedy this.

any help is apreciated.

Thanks

take care

Roy.

[rplum]

No one has responded to this issue in a month and Shopify has once again sent e mails to my clients referencing this deprecated call.

As far as I can tell, the deprecation is regrading a field that I do not use or reference.  I only get this deprecation notice for this call when the store has multiple locations enabled.  this same call for single location stores has no deprecation notice.  From my end, the calls are identical.

Deprecation deadline to 3/1/2022.

Doe ANYONE from Shopify look at these messages?

Please help.

Roy.

[csam]

Hi @rplum,

I haven't been able to replicate this, so we're going to need a little more info in order to investigate the expected behaviour here - could you please fill out the Report an Issue form found under the Partners Support section? Any additional information you can provide around this issue would be very helpful, including an x-request-id from the header of a recent request.

Thanks!

[rplum]

Thank you for your reply.

I have created the support request in the partners portal.  I made the request just now  so it is not old.

I am unable to figure out how to save all the response headers in a file without writing code to do so, but I believe you are interested in this header:  X-Request-ID: 6b0847c8-ae60-4883-b70c-9bcfbaaffc4b

I had redone the call using postman, which allows me to save the response json, but not the headers.

the rest call is a simple GET so there is no request body.

I understand the deprecation issue is about a field that is deprecated, but I am not asking for or using this field in this call.

this same exact call on another client's store does not have any deprecation message, so it appears to be related to store settings, and not the call itself.

thank you for your help.

Roy.

[bnixongm]

I am also getting this deprecation warning and am unable to stop it. It started with API version 2022-01, but even now with 2022-04 it persists.

Example:

GET https://redacted.myshopify.com/admin/api/2022-04/orders.json?limit=250&status=open&created_at_min=20...

x-shopify-api-deprecated-reason: https://shopify.dev/changelog/property-deprecations-in-the-rest-admin-api-order-resource

x-shopify-api-version-warning: null

This doesn't make sense to me because I am not explicitly requesting the deprecated fields, nor is it possible to implicitly exclude them without excluding the whole customer property of the Order resource, because the API does not support explicitly requesting embedded fields, only top-level fields.

[Milo-7]

Have you solved this problem? We have also encountered the same issue.

[Milo-7]

hi,Have you solved this problem? We have also encountered the same issue.

[bnixongm]

I just hard-coded an exclusion into my API request code so it ignores these particular deprecation warnings.

[WojtekKru]

I'm also getting the same deprecation message even when I explicitly request only `id` field.

$ curl -v -H "X-Shopify-Access-Token: sh***" https://***.myshopify.com/admin/api/2022-10/orders.json?fields=id
< date: Mon, 23 Jan 2023 10:43:35 GMT
< x-shopify-api-deprecated-reason: https://shopify.dev/changelog/property-deprecations-in-the-admin-api-order-and-lineitem-resource
< x-request-id: 263776bd-5375-4fa6-82b9-f9789fa41eec
* Connection #0 to host ***.myshopify.com left intact
{"orders":[{"id":4678661996580},{"id":4678654328868}....

[Milo-7]

Have you solved this problem? We have also encountered the same issue.