Method:API Q&A

Re: Method PUSH/API Call Limitations?

Method_Michael — Fri, 10 Feb 2012 16:59:25 GMT

Sean-

This ended up being a Method platform issue which should now be resolved on the stage site.

-Michael

Re: Method PUSH/API Call Limitations?

Method_Michael — Thu, 19 Jan 2012 14:14:26 GMT

Sean-

Try putting a counter in the loop to count how many times the loop runs and compare that value with the total number of records that should be processed.

-Michael

Re: Method PUSH/API Call Limitations?

voltaire — Tue, 17 Jan 2012 20:11:07 GMT

Yes, I've been working in the January version for the last week or so. It's very random in terms of when records are skipped. I've been looking for patterns, but I can't seem to find any. I could have problems after the loop has run through a couple hundred transactions, or after I've done a couple thousand, or not at all. It's across the board really.

The biggest problem that this creates is once this happens, I'm unable to go back in and run a loop on any of those failed transactions. I've also tried running a loop that was different than the original loop to see if I could connect to that transaction again, but the record won't update automatically. It's as if QuickBooks doesn't recognize them at all anymore. It seems to require a manual manipulation, but obviously for hundreds or thousands of transactions that need to be re-coded, that's just not feasible.

Sean

Re: Method PUSH/API Call Limitations?

Method_Michael — Tue, 17 Jan 2012 15:09:41 GMT

voltaire-

Have you tried this on the staging site? You can get to the Staging site by clicking on "Switch to the January Version" at the bottom of the login form. (Click Here for more info on this).

There was a issue that was addressed that in some cases caused records to get skipped when conditonal statements existed within a loop. This issue is fixed in the January version.

-Michael

Re: Method PUSH/API Call Limitations?

Method_Michael — Tue, 17 Jan 2012 14:40:31 GMT

voltaire-

You are doing this through Method actions correct?

As far as I know there is no limitation to to how many records can be pushed but I will test this further. What would you say is the number of records you have to process before this becomes an issue?

-Michael

Method PUSH/API Call Limitations?

voltaire — Mon, 16 Jan 2012 19:43:21 GMT

Is there a Method PUSH/API Call limitation of some kind?

I'm using a loop action in Method to update a large batch of transactions in a client's QB file. Although the loop action (including pushing updates to QuickBooks) starts off working well, Method stops updating QB after it has already processed a large number of changes. In effect, the records in Method are updated, but the changes will no longer push to QB, and after that the changes won't ever reflect in QB even if I do a partial sync or a full sync.

I notice that Method PUSH will pause for a bit, sometimes as much as several minutes, and then it will start pushing changes again. However, at some point it either skips over transactions, to update others, or it just stops processing altogether at some point. Is this possibly an issue with just queuing too many changes at one time? When I'm working with a smaller number of transactions, I tend not to run into this problem.

This seems to be the case for different types of transactions including JournalEntryLines, BillExpenseLines, etc. I am finding no conflicts to resolve under the QuickBooks Tab.

Thanks in advance.