Method Community

Hi Lance, that is not possible via the API today.

As part of troubleshooting this ticket we generated a quick PHP sample - see here: https://www.method.me/api/ (right hand side, bottom).

We discussed some good points for clarification: - Stuart is 100% right, the IsWaitingForSyncApproval field needs to be set to No (or false), or it will not Sync.  The red herring comment was strictly in reference to forcing data to be sent to QuickBooks with the API.  That requires ...

Hi Stuart, I believe the suggestion from Support is a bit of red herring in your case.  Setting and resetting IsWaitingForSyncApproval will not result in the SalesReceipt being "Pushed" (automatically synced) to Quickbooks. There is a call in the API that is meant to take care of this.  It is called ...

I'm going to reach out to you directly.  

I should have reviewed your code before responding.  My read of your code is that the Contact section is creating the problem and should not be executed.  When you create the Customer you are creating the first Contact for that Customer automatically.  You do not need to execute the Contact section of your code (everything ...

I haven't reviewed the code you provide but I suspect I know what is happening.  There is a bit of business logic that needs to be included to make Contacts work properly.  In short, Contacts should (must) always be associated to a Customer.  However, the API does not prevent you from creating a Contact without associating ...

That's an interesting idea.  The API itself does run behind a load-balancer and is deployed on multiple servers.  However, the servers themselves should have the same code deployed (and there are controls in place to ensure that is the case).  The individual servers can be up or down at various times throughout any given ...

I don't believe the issue has come back.  I'm assuming CoursePayments is a custom table you created, is that right?  I created a table with the same name, added some fields and everything seems to be working as expected.  I'm guessing there may be an issue with your specific implementation.  Can you share any ...

Deleting a Contact is straightforward.  You simply need the RecordID. You can query all Contacts as follows(if you have a lot consider a Where clause to narrow the search, also include the Fields that are meaningful to you): <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" ...