-
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?
-
It appears I spoke too soon. (Actually I was looking in the completely wrong place when I was testing it out).
I tried to create a dropdown field in the customer table and I still get the "An error has occurred. An email has been sent to Method staff. If this problem persists, please contact the Method Team at ...
-
Yes, that should be the message you get in both the MethodAPIUpdate and the MethodAPIInsert.
-
It appears to work now. Now I get "This insertion will violate a requirement that the record in the destination table must be unique."
I also noticed that some of the other messages about a record not be unique have been changed to the same new message. Is this going to now be the standard message?
-
Updates are up there now (we were about to do an update anyway).
Want to give it a try?
-
Thanks Paul. Can you please let me know when you have that updated, so I can change my code to handle the duplicates.
-
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 ...
-
-
Conrad,
To use the calendar-recurrence object you’ll need to first make sure there’s a calendar object on the screen and the properties have been set up correctly, if one doesn’t exist go ahead and add one. By completing steps 1 through 7 of the calendar wizard you’ll notice it requires you to select the main table that ...
-
Matt - can you try doing it again. Let us know when you do, and we'll search for the error message.
Thanks,
Paul