Method Community

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 ...

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 ...

All data issues with affected transactions should now be resolved.

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 ...

Hi Christina, I'm going to reach out to you directly to see if I can help move this forward. Regards, Peter

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.

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

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

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

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, ...