Missing location id in transactions in the graphQL API

GraphQL Admin API Troubleshooting
1

Hello!

We have a really particular case for a client where an order could be partially paid at a location or online and then the customer could get to a store and pay at a different location.

At the end of the day we need to get all transactions and send them to a third party system based on which location made the transaction.

The transactions rest API does have the location_id, but the graphQL API is missing that information.

I was about to use Matrixify for that but the answer from their dev was that they are migrating to graphql and that this field is missing from the graphql API which is why they didn’t add this particular field. So now we are stuck to code something to get the location ID from the rest API :sweat_smile:

2

Hi Tommy,

Our team are aware of this current limitation and will be addressing it - for now you will need to continue using REST for this.

3

I have run into the same issue using the Stitch integration which is built off of the Singer tap. We’re currently having to run the REST API integration for all of our tables other than products, product_variants, and inventory_items which have been deprecated in the REST integration. We will require the location_id to be able to move fully to the graphQL API. Any idea on a timeline?