Method Community

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

I wanted to add a note to this thread about working with Customers and Contacts.  Customer to Contacts is a one-to-many relationship.  That is, one Customer can have many Contacts, but a Customer must have a least one Contact.  That is enforced by the Method UI and API, both create a Contact when a Customer is created. ...

Let's walk through the process of figuring out what to submit to the API.   Step #1 - Identify want we want to create - in this case Opportunity Step #2 - Query the field list for Opportunity <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:tem="http://tempuri.org/"> ...

My appologies for being slow to response.  This is an excellent question.   The short answer is FullName - you need to include the FullName of the Customer you want to link to the Opportunity.  In a subsequent post I'm going to attempt to explain how you can figure this out.

Note that this thread uses TenantID.  This is only relevant for customers who have a multi-tenant Method:CRM account.  If you are unsure if you have a multi-tenant account you likely don't, the majority of customers do not.   If you exclude TentantID from the example above it should work fine for most users.

The error is caused by the formatting on the strings in the Arrays.  They are: <string>something</string>.  They need to follow the formatting of the parent: <tem:string>something</tem:string>.  There is a subsequent error that Name is a required field on the Customer table.  Also, the ...

I appreciate that Jim, by the way does it also works for budget management? some sort of quickbook plans for all your expenses, savings and earnings.. not so much that familiar with Method so I am kinda not aware of everything.

This is huge - thanks , Peter for working on this!

Glad to hear it, William!

Thanks, I also have the same concern, good that I was able to get the solutions from here.