Sep 2010
15 / 15
May 2011
May 2011
consolibyte
Sep '10

We are testing a QuickBooks integration service for e-junkie, and would like to use the E-Junkie internal transaction ID when pushing the data to QuickBooks.



Unfortunately, it doesn't appear that the internal transaction ID is being sent to us in the HTTP name/value POSTs.



Can this field be added to the name/value HTTP POSTs?

E-junkie_GuruWebmaster & Support Guru
Sep '10

We can put that on the wishlist for Development, but frankly, it wouldn't be likely to get implemented soon if at all. Our Integration submissions are designed to mimic the format of PayPal IPN as closely as possible, and that internal ID would not be part of a PayPal IPN, so it would have to be one of the very few non-IPN "additional variables" that we add to the basic IPN data set. Is there a specific purpose for which you'd need to use that particular ID, rather than the actual Transaction ID or the Invoice ID?



The only reason we even generate or log an internal ID at all is so we can provide a reference number to affiliates for each sale in their commission earnings reports (e.g., in case they want to contact the merchant about a particular sale they referred), without revealing those sales' actual Transaction or Invoice IDs which unscrupulous affiliates could conceivably misuse.

consolibyte
Sep '10

Hrm, bummer, not what I was hoping to hear.



We do integration of shopping carts with QuickBooks and QuickBooks Online, and were looking into doing an integration with E-Junkie. We currently support a number of other shopping carts such as Foxycart, WHMCS, Ultracart, Infusionsoft, etc. You can see our sign-up process or sign up for a demo at the link below:

https://secure.consolibyte.com/



We were hoping to build a similar solution for E-Junkie so that people could pay a low monthly fee and have their orders pushed into QuickBooks automatically. However, QuickBooks has an 11-character limit on it's order # field. Your invoice IDs and Transaction IDs are too long to fit in the QuickBooks field. :frowning:





Is there any other sort of ID I could use that will fit within QuickBooks' 11-character limit?



Or, would E-Junkie be interested in building some sort of custom data feed so that we can build a QuickBooks integration solution that works with E-Junkie? I'm sure that you have client's who would be interested in this feature.





- Keith Palmer

keith@consolibyte.com

https://idnforums.intuit.com/messageview.aspx?catid=56&threadid=9164

https://code.intuit.com/sf/projects/phpdevkit

http://www.consolibyte.com/

https://secure.consolibyte.com/

E-junkie_GuruWebmaster & Support Guru
Sep '10

I've brought this to our Development team's attention, so as things stand now, we're just waiting on them to consider the matter and weigh in.

consolibyte
Sep '10

Thanks, I appreciate it. I'm definitely very interested in building this- I have one of your customers testing it already, and it's working really great for them. I'm sure there are other people that could use the service as well (QuickBooks integration is great selling feature for your cart!).

E-junkie_GuruWebmaster & Support Guru
Sep '10

We still haven't heard back from Development about this, but just thought I'd offer a suggestion that in case we cannot accommodate your request soon enough, you might just generate your own order# to fill that field, and perhaps save the actual Transaction ID in some other arbitrary data field of adequate size that may be available to use. Also, one of our Support team used to work at Intuit years ago, and he seems to recall that the QuickBooks Enterprise solution may be able to accommodate larger entries for the order# field even if the basic QuickBooks product cannot.

consolibyte
Sep '10

Thanks. Yes, what we're actually doing now (generating our own order #) but it makes it extremely difficult to match up orders between QuickBooks and E-Junkie when you have to constantly go back and forth and say "OK order #1234 is really #6789 ...". It's clunky, and disappointing given that it seems like it might be a very simple thing for you to fix.



Maybe E-Junkie could just add a checkbox:



[X] Also send internal transaction ID with this feed



So that you could both maintain current compatibility for everyone, and also support integrations that require the use of the internal transaction ID?





The current limit in all desktop versions of QuickBooks is 11 chars, including Enterprise. QuickBooks Online supports 21 characters.

pixelan
Sep '10

Development has confirmed that we do not presently include the E-j Internal Txn ID with our custom/3rd-party Integration submissions, but we should be able to add that with the release of our next major code revision, which they're working on presently.

E-junkie_GuruWebmaster & Support Guru
Sep '10

Development has confirmed that we do not presently include the E-j Internal Txn ID with our custom/3rd-party Integration submissions, but we should be able to add that with the release of our next major code revision, which they're working on presently.

7 months later
ellen
Apr '11

Hi everyone,



Sorry this one has taken so long--it, along with some other feature requests, has been stuck on needing a change in the admin panel, and that's still an ongoing project.



Because the underlying change is so simple (two lines of code added), we've gone ahead and implemented it. However, we figure some people's scripts may not deal well with having a new variable unexpectedly show up, so we're only activating it on a per-client basis.



SO: If you'd like us to start reporting this variable (I've named it "ej_txn_id") for your account, please post here explicitly requesting it, or email development@e-junkie.com, and we'll turn it on for you. Keep in mind getting it turned off will require the same process, so you'll want to make sure your scripts will handle it properly first, or the change could break all of your notifications...

ellen
Apr '11

Ok, I've enabled it for you, G&G. Please let us know if you have any problems with it!

17 days later