Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

locations in Quickbooks connector

Answered
Dan Leng User

Connector name: Quickbooks

Table name: location, and location_id that links to location in transaction link tables like journal_entry_line

API documentation link:

https://fivetran.com/connector-erd/quickbooks

Additional details:

Filing in response to this question: https://support.fivetran.com/hc/en-us/requests/382930

Original Question:
------

Hi Fivetran Support,

We're using your QuickBooks connector and have run into a gap: the location table (and location_id on transaction lines) is not appearing in our connector schema, even though "Track locations" is enabled in our QuickBooks Online account.

We've already tried reloading the schema — the location table simply isn't offered. For context, we can see department and class syncing fine, but Location is a separate dimension in QBO and we need it to accurately tag transactions by market/region in our data warehouse.

Could you confirm:

Does the QuickBooks connector support syncing the location table and/or location_id on transaction line tables (e.g. journal_entry_line)?
If not, is there a roadmap item for this, or a workaround you'd recommend?
This is blocking our finance reporting pipeline, so any help is appreciated.

Thanks,
Dan

Please sign in to leave a comment.

Comments

1 comment

Date Votes
  • Official comment
    Sandeep Preetam Saila Fivetranner

    Hi Dan, 

    Thank you for raising this — we looked into it carefully. QuickBooks Online's REST API doesn't appear to expose a standalone Location endpoint that we can sync as a table. Location tracking in QBO is typically implemented through the Class or Department dimensions, both of which Fivetran already syncs today. 

    Could you help us understand what you're seeing? Specifically: 

    -  When a transaction has a location assigned in QBO, does it appear under a Class or Department field, or is it a completely separate field? 
    -  Do you have a link to the QuickBooks API documentation for the Location endpoint you're expecting? That would help us confirm whether this is something their API exposes and how we could implement it. 

    Best,  
    Sandeep