Method Community

Good to hear.  It was nothing from your end.  The actions used to get the correct RecordID of the invoice were a bit off.  Instead of passing the Transaction.TransactionRecordID to the invoice, it was passing the Transaction.RecordID - wrong field.  So it was our design mistake with your version.  Glad to hear that ...

Kieran - thanks for your email. You should be good to go now. If you are signed in, try signing out and trying again. Paul

Hey Kieran - let me see if I can help out, so that we can get you going over the weekend. If you want to send that info today, just email it to method at methodintegration dot com and I'll have a look. In terms of speed, I highly recommend you download FireFox and use that instead of Internet Explorer.  FireFox is free ...

Matt - sorry, this post fell through the cracks. You are most likely receiving that message because you passed an empty field name.  My guess is that you split a comma separated string into an array, and the last field still had a "," after it. For example: field1,field2,field3,".Split(",") would actually ...

Hey Matt -  It looks like you are trying to insert DueDateStart twice in the same insert statement. Paul

 We're getting a message that the field you are creating already exists.  Just made a couple changes on the backend to put that into the response message.  Are you getting a more informative response if you try again now?

 Yes, that should be the message you get in both the MethodAPIUpdate  and the MethodAPIInsert.

Updates are up there now (we were about to do an update anyway). Want to give it a try?

 Thanks Matt. Looks like the problem was that you were inserting records like "Friday" into a table that already had "Friday".  Since that table had the field marked as unique, it caused a unique index violation. So there's you reason. We'll put more info on the returned message so that you actually get ...

Matt - can you try doing it again.  Let us know when you do, and we'll search for the error message. Thanks, Paul