Method Community

Ok cool glad you recognize the flaws, hopefully I will not have to call on you to be a log reader in the future :) Thanks

[quote user="Method_Paul"] -OR- after you created all your invoices using the API, sign into Method, and have a screen that loops through all your new invoices and emails them - here you can use the "Generate Report" action where the action result will contain the location of the PDF it created, and in the "Send ...

Agreed. However, it's not as easy as just delivering the raw error that we get, as that can potentially be a security risk as it may give out server configuration details. So our job is to parse common errors and turn them into meaningful messages. That hadn't been done for the error above, so you just got the generic "we haven't ...

Hmm.. at least output some useful error info within your api.

Top secret! ;)

Thanks Paul, how do I see the error logs so I don't have to bug you guys. :) Thanks

Can you make sure that the fields listed in your insert are unique. Looks like there are error logs suggesting 'BillAddressAddr1' is specified twice. Paul

This is the error I am getting when trying to insert a new customer record. with the MethodAPIInsertV2 api call. I have no clue what the error is, any way to find out? Do I first need to create a company record in order to add a customer record?

Thank you for the reply. I'll have to give this a shot. In the meantime, I've looped through the Estimate table and pulled out the maximum TxnNumber. I then increment this and stick it in the Estimate # object which links to the RefNumber. Method seems to have no problem with me sticking an integer into a text field, I just can't do it ...

Johnny, If you select the January version of Method (select "Switch to the January version" at the bottom of the login screen) you can actually use a SQL override to sort the RefNumber of the sales orders in the grid.  You can cast the field as integers.  Method will then sort accordingly. A note about ...