Method Community

Thanks John for the post.  You have a good point.  How do you manage customers with multiple contacts?      The Work Order is actually an Activity.  In a Work Order, the Customer field is actually from the Entity table and is filtered on the screen only to show Customers.  I'm assuming you have the ...

Mark - we don't have this on roadmap for the current version of Method, or the API. However, once the dust settles on all of our current projects (and you know....we've got a lot on the go that have to get finished first), we can open this up for discussion.  Paul

We will surely look into your message and make it better. Cheers!!

Manish, Paul, Every function call works fine. I'm getting valid XML response. This is almost definitely an issue with a blacklisted IP address on your end. I am sending you AND Paul a private message with some information that will help you debug.

furrywombat - Looking into this. Are you able to directly browse the api using https://www.methodintegration.com/methodapi/service.asmx and invoke a function?

Manish, Please check the server settings for any recent blacklisted IP entries. If you're seeing this as resolved, and I am not, I wonder if any one of your servers is preventing calls coming from ours for whatever reason. Again, going back to my assertion that this whole thing started when we made a massive call to the item database. It ...

Manish, The issue has not been resolved. I am still not able to connect. Still getting error: PHP Fatal error: 'Function ("MethodAPIFieldListV2") is not a valid method for this service' 

furrywombat - This has been resolved. Hope we got back to you in time. Please let us know if you are still having problems with the API.

Paul, I understand intimately the focus required. Just wanted to make sure this wasn't flagged as resolved, so will wait to hear from you. Interesting timing on the data call vs. blunder. The exact second that call was made, it stopped working. Take your time. Will patiently await your reply.

furrywombat - fully working on this.  Sorry for lack of communication - head down in solving it. BTW - the problem wasn't caused by your large data call. Totally unrelated.  Not security related either. It was a dev ops blunder.