Quickbooks API for Drupal 7

Hey mate,

Looking into a project whereby we'd utilise the Drupal 7 version of this module. If we end up going down this path with the client it will be committed back to the platform so we'll hopefully be able to get some solid testing in etc.

Bit hard to investigate however pre-project since we're not running on Quickbooks ourselves. Are there any large hurdles you can see bringing the functionality across at this stage, or is it just a matter of having the time/cash to do it?

Cheers for any reply! Hoping to get the client onboard to help out :)

I'm working on a site for a very busy small company, I've been looking at ECC but... yeah. Our site is D6 so far, but no doubt will one day end up being D7. I'm not massively experienced but I can help test and make patches with git.

I have been using Drupal 6 and 7 for almost a year now, and I am not en expert coder but I am not retarded by any means, and have been looking to spread my coding wings. I also have a project coming up for my company whereby this Quickbooks integration would be extremely handy. Is there anything I could do to help that may be within my skill level?

Aaron

Hello Nataniel,

Have you seen this: http://drupal.org/sandbox/stephen.colson/1100862? What do you think of it?

What is the status of this? I have a project where quickbooks integration will be essential in the "mid-term". Would love to contribute and participate where I can.

Just want to pass invoices back to Quickbooks from a heavily modified Drupal Commerce for in-house accounting purposes. Nothing special. I would have to port it over to D7, but if it is a working product then I can work from there.

You might want to take a look at the qb_user sub module. It looks like that sub module maps user accounts with quickbooks data. Module description: "Synchronize Customers, Employees or Vendor contacts from Quickbooks to your Drupal site."

I would LOVE this feature for d7. Any idea if you plan on moving forward on further d7 integration for this project?

I have been trying to test the basic functionality of the patched module put out by Nathaniel. For now, I am testing against a local installation of QB 2012 pro using a sample QB file (and a local Drupal 7.22).

It seems the qb and qbwc modules are basically fully functional. So I have been messing around with the data and field module. It seems for the data module to really do much (without custom writing another module), it NEEDS a field which refers to a stock query. I made a field that refers 'customers'.

This is where I start having issues. It seems that the data module gets the data (qbXML) for each customer on syncing the first time. Syncing a second time (as an auto-run would do) causes drupal's response (to sendRequest) is

<?xml version="1.0"?>
<?qbxml version="7.0"?>
<QBXML><QBXMLMsgsRq onError="continueOnError"><CustomerQueryRq requestID="1"/><CustomerModRq requestID="2"><CustomerMod><ListID>6E0001-1197764528</ListID><Name>Adam\'s Candy Shop</Name></CustomerMod></CustomerModRq>
...

The important part of this is the fact that (if you use the QBSDK xml validator, you can see this, or just examine the .xsd files) a CustomerModRq requires an EditSequence, which is not set by default when initially loaded.

My question then is what is the design of EditSequence (AKA qb_edit_sequence column of the qb_data_value table)? Is the qb module suite supposed to only have an edit sequence at certain times (such as when a value is updated), or is this a value that SHOULD be synced with QB? Also, it seems that if the EditSequence cannot be set (in time to generate the qbXML), the qbXML generator should not be able to generate a node incorrectly (i.e. a CustomerModRq without an EditSequence).

After a little futsing with the the code, I used a line that actually allowed syncing the value with QB. Problems with this are that I haven't had time to look into any side effects of doing this, there is likely a better place to do it than where I did (such as in the original import, not as a check during operation testing).

My feeling about this issue is that this is a bug that the qb_edit_sequence is not synched with QB. I think that QB uses the EditSequence as the equivalent of drupal's 'vid' for the revisioning system. Or am I missing something?

Looking into this further, I have a bit more information:

1 - The Edit sequence seems like something that QB sets, and it is nearly constantly changing - like a timestamp, but with a different epoch.

2 - _qb_data_qbwc_response (in qb_data.wc) appears to get the editsequence value, and 'save it', but the saving is done within a DB transaction, so it is not finalized.

3 - qb_data_value_save (in qb_data) seems to unset this value for the sake of disallowing non-QB maintenance on anything other than a select few fields - this is done before the transaction is finalized.

Any suggestions on where this should be fixed? Add functionality to differentiate whether the information being saved is coming from QB or Drupal (users, forms, modules, alters, etc...)?

Is anybody does quickbooks integration with drupal 7?
With full of functionality like- adding customers to quickbooks account, invoice update, alter products quantity detail etc.

http://www.webgility.com/ecc/quickbooks-ecommerce-connector.php

We had a foray into swapping from sage to quickbooks and considered this. At the time there were a few pieces of the puzzle missing. They offered to fill them in for a bounty or when enough people ask. Looks like more people asked or someone paid up because they sent us an email to let us know ECC now connects with Ubercart for D6 and does everything we need it to. Too late though, we've gone with Sagepay.

Drupal 7 module
https://www.drupal.org/project/qbo_api
Quickbooks Online API