Method Community

I have invoices that synced, generated an invoice #, and then we make a change to the invoice and there's conflict (and the invoice number goes away).  We've made changes to invoices for months without any problems.  There's also an invoice that's in our QB that doesn't appear in Method at all. It was created in Method.  It has a Method invoice number assigned, but when I go to find it in Method, the existing invoice table skips that invoice number in its sequence.

My office is trying to create invoices that often need to get changed and it's causing problems...

cpitts-

What's the date on that invoice? Does it maybe fall outside of the transaction history you set in Method? (QuickBooks > Synchronize).

When you are making changes to these invoices are you making the changes in QB or Method? What conflicts are the invoices generating?

-Michael

No- an invoice today, and one created a couple weeks ago (our transaction history goes back to beginning of '11).

Changes are being made in Method, and the conflict reads:

QuickBooks returned an error when adding/modifying a accInvoice record. The error was: There was an error adding, modifying or deleting 21ECA-1312839866 because it is already in use. QuickBooks error message: The transaction could not be locked. It is in use by another user.. The Request was: <?xml.

Our office is small enough for me to check that there was no other user (in QB or Method) involved, interested, or even knowledged-in these invoices-- and no reason to be.

cpitts-

If you click Un-Delete for that conflict does it go away and allow the modification or does that conflict return?

-Michael

It returns.

cpitts-

This conflict message comes straight from QuickBooks and it is not something Method can control, it's basically telling you that the change you want to make can't be done because QuickBooks is still using the record. Method tries to push the change but if QuickBooks has the record locked then Method can't apply the change.

Try closing out QuickBooks on all computers reopening it on the Main sync computer and then Un-delete the conflict, you may also want to try it in single user mode temporarily to see if it still causes conflicts.

-Michael