|
|
|||
|
|||
|
It would be great to be able to drive QB classes from CommitCRM. I would like to be able to set a class on each item, and have that push over to QB.
I know the answer is going to be "do this in QB" - and I would be OK with that, BUT... To specify a default class on an item basis requires QB Enterprise - which is quite expensive, and completely unnecessary for most of us. I know the QB API supports setting the class, but I'm not sure how difficult it would be for you guys to drive this from CommitCRM. Anyway, consider this a feature request with my vote. :) |