TL;DR: use|map "fulfillment_status" and "financial_status" to NULL if you would use "any".
A tmp solution for a search by "name" (aka increment id) is
to disable (NULL) the two params, but keep the "status" : "any".
NULL actually should mean that your http client will not send this param.
Why:
"fulfillment_status" and "financial_status" are by default "any".
(See https://shopify.dev/docs/api/admin-rest/2023-10/resources/order#get-orders)
BUT "status" is by default "open". So you would get different results without a status" : "any".
I tested this with our dev shop and i got all (different status) orders with the 2 NULL-params.
So not using those 2 params (still) means by default "any", as documented and expected.
Find by name example:
// Example params to search an order by "name" : "ABC1234"
array(
'name' => 'ABC1234',
'ids' => null,
'since_id' => null,
'status' => 'any', // KEEP!
'fulfillment_status' => null, // DISABLED 'any',
'financial_status' => null, // DISABLED 'any',
'created_at_max' => null,
'created_at_min' => null,
'updated_at_max' => null,
'updated_at_min' => null,
'processed_at_max' => null,
'processed_at_min' => null,
'fields' => null,
'limit' => 50,
)
// Then check if result count = 1 and result[0][name] = {expected name}
As for search functions that filter by dynamically params:
you could map the 2 params "fulfillment_status" and "financial_status".
PHP code:
$options = {get the options as usual}
foreach (['fulfillment_status', 'financial_status'] as $offset) {
if (isset($options[$offset]) and $options[$offset] === "any") {
$options[$offset] = null;
}
}
So your "any" search, which is now broken, is just using the default (working) "any".
