Search results by user ID 11597

Re: Leads not generating in Method

Method_Peter — Mon, 05 Feb 2018 13:55:06 GMT

For anyone following this thread, we sorted out the issue. The issue was with the user account being used in the API call.

As a troubleshooting tip for anyone who finds themselves in a similar situation, if you were able to use the API and it stops working it is a good idea to verify the user account and password you are using to access the API are still valid. To do this I like making a very simple API call with Postman . Although Postman isn't the best tool for working with SOAP APIs it probably is the easiest tool for making simple http(s) requests. I like to use the TableListV2 call from the Method API when verifying access to the API is working (I use TableListV2 because it simply retrieves data, there is no risk of accidentally breaking something). I can construct a very simple request like what follows and POST it to https://www.methodintegration.com/MethodAPI/Service.asmx . The response should contain a message that will help troubleshoot any issues accessing the API.

Request:

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<MethodAPITableListV2 xmlns="http://tempuri.org/">
<strCompanyAccount>{{CompanyAccount}}</strCompanyAccount>
<strLogin>{{Login}}</strLogin>
<strPassword>{{Password}}</strPassword>
<strSessionID></strSessionID>
</MethodAPITableListV2>
</soap:Body>
</soap:Envelope>

Response (if the password is not correct):

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<soap:Body>
<MethodAPITableListV2Response xmlns="http://tempuri.org/">
<MethodAPITableListV2Result><?xml version="1.0" encoding="windows-1252" ?><MethodAPI response = "Failure. The API could not validate your log in. Please make sure you have entered the correct Company Account, User and Password, and that each are spelt correctly. Also, ensure that this User has been configured for Method API access by going to Customize > Users, editing the User, and ensuring that there is a check in the 'Is Allowed to Connect via MethodAPI' checkbox." ></MethodAPI></MethodAPITableListV2Result>
</MethodAPITableListV2Response>
</soap:Body>
</soap:Envelope>

Re: Creating a Sales Receipt from our website using API

Method_Peter — Tue, 30 Jan 2018 22:14:48 GMT

The issue appears related to MethodAPIActionSendToDesktopV2. Even though the real-time sync is not initiated when MethodAPIActionSendToDesktopV2 is called (becaue of the previously mentionend issue), it still needs to be called after a transaction and the transactions lines are inserted to ensure the transaction gets picked up by regarularly scheduled sync (Changes-Only and Full).

This is can also be accomplished by editing the transaction in the Method:UI. This appears to be what was happening when IsWaitingForSyncApproval was edited.

Re: The item is placed in the request in incorrect order

Method_Peter — Tue, 16 Jan 2018 15:01:36 GMT

All data issues with affected transactions should now be resolved.

Re: The item is placed in the request in incorrect order

Method_Peter — Fri, 12 Jan 2018 21:39:31 GMT

The issue was addressed in a hotfix released this morning. Any newly created transactions should work as expected. Any transactions created, that subsequently had line items deleted, during the approxemately 24 hour window from 9am Jan 11, 2018 to 9am Jan 12, 2018 may be effected. We are continuing to work to identify affected records and correct the data.

Re: Leads not generating in Method

Method_Peter — Fri, 12 Jan 2018 21:21:49 GMT

Hi Christina,

I'm going to reach out to you directly to see if I can help move this forward.

Regards,

Peter

Re: The item is placed in the request in incorrect order

Method_Peter — Fri, 12 Jan 2018 14:34:40 GMT

Just an FYI for everyone - there was an issue with the Method release yesterday. It is being addressed, we should be announcing a resolution shortly.

Re: Field Size change not working in API

Method_Peter — Wed, 03 Jan 2018 18:18:19 GMT

Hi Mike,

Clearing the cache was a good thought. What table are you working with? If you run a MethodAPIFieldListV2 for the table does the Description reflect the size change you made?

Regards,

Peter

Re: Auto transfer screens

Method_Peter — Fri, 15 Dec 2017 19:43:47 GMT

An entire tab cannot be transferred, screens can only be transfered one at a time.

Re: Auto transfer screens

Method_Peter — Fri, 15 Dec 2017 15:49:16 GMT

Not through the API, but is possible in Method:Classic.

Re: Creating a Sales Receipt from our website using API

Method_Peter — Thu, 14 Dec 2017 21:20:53 GMT

i Stuart,

1. Correct

2. MethodAPIActionSendToDesktoV2 needs to be called to Sync the Sales Receipt in 'real-time'. If you don't call MethodAPIActionSendToDesktoV2 (or can't because it is broken) the Sales Receipt will get picked up by the next Changes-Only (typically, syncs every 15 mins) or Full (typically, syncs once a day) Sync. You are correct that the call must be made for each individual Sales Receipt using the RecordID.

3. Correct. The next time Sync runs (either a Changes-Only or Full Sync) any records that have been updated since the last Sync (including, but not limited to, any recors created via the API) will get picked up and Sync'ed.

4. Correct. MethodAPIInsertV2 will add a record to Method, and MethodAPIActionSendToDesktopV2 will trigger the change to be sent to QBDT. Similarly, you could call MethodAPIUpdateV2 to update a record in Method, and then call MethodAPIActionSendToDesktopV2 to trigger that change to be sent to QBDT.

Regards,