Project status

Hi Chris,

I haven't been able to get to this recently ( it's largely a scratch-my-own-itch thing, unless there's funding ). I'm mainly interested in discussion. So there's not much, if anything, new.

The first order of business is getting the QWS process working cleanly. Basically, modules can make their intent to communicate - and their data - available via hooks.

The API module won't have any business logic. It would make more sense for e.g. Ubercart to maintain its own data for inventory, sales, payments, etc; and then report back to Quickbooks as needed via a module of its own. Writing an integration as part of the Quickbooks module would require too much work to reach out and touch Ubercart or other data providers.

That said, I'm considering shipping some sort of a mapping module. In this case, I'm thinking of creating a field that links to QB's internal ID, and, using that ID, makes the rest of the data from that record available to other fields on your node. Thus, you'd link a profile node to the "john smith" customer record, and your first_name field is populated with "John", and your field_last_name is set to "Smith".

I'm toying with using similar models to integrate with external sources here and here.

Beyond that, I'm open to ideas and the like.

Hello Allie,

I just posted a patch (http://drupal.org/node/298079) that includes the work we've done for your module in order to build a separate ubercart integration module.

Please take a look when you have a chance.

Thanks!

Thanks!

I'm closing this as there's not much left to do here.