A space to discuss GraphQL queries, mutations, troubleshooting, throttling, and best practices.
Hi,
Our app is getting a list of order details for printing.
We already have a list of the order id's, but this does not seem to help much since we cannot find a way of having these as a query input in a bulk operation.
So now we have to filter on a created at range which might produce tens of thousand extra orders that we don't want.
Anyone that has a solution to this?
Bulk processing for printing is something I have done for years. The way I do it is very simple, and works like a peach.
- More Actions link in Admin for an order (one ID)
- Bulk Actions link in Admin for many orders (a list of order IDs)
- App is provided with a list of order IDs (iterate the list and print each order)
The problem with label printing is deciding what is printed. Simple order details like an address or something is one thing, but line items is another
As for a bulk query, having an explicit list of ID is not helpful. You'll either have to ask for them in bulk by date range, or other status, and then when you receive the JSON with the whole shooting match, filter yourself. At least that is my opinion. So either you cherry pick using your ID list (I would do that) making a GQL call, print, move on, or you wait for all the orders possible with your set, and then filter and print. Either way. This is hardly an intractable problem.