-
Notifications
You must be signed in to change notification settings - Fork 310
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Invoices require a valid email if present #477
Comments
Got the sample invalid email? We can either do a basic regex validation (contains @) or a more complex RFC based one; but if it doesn't match the underlying API perfectly; it might be better to do the simplest approach. |
Hey @Samsinite, a contact will always require a valid email if provided. That appears to be the basis of this issue. An invoice relies on a valid contact, so that's going to fail if the contact is invalid. I see two issues to fix here:
|
Here is what the API response looks like in this case (single invoice, single contact):
|
Hi, we are encountering a validation error on a contact when batch creating a set of invoices, apparently this requires that the email address is valid if one is present. Was actually surprised to see this error as there was no associated error when we saved the contact model. Even stranger is that the validation error is nested under the contact even though that contact was already created. I have the response xml that I can likely provide (as long as I remove sensitive information) if that helps. I am going to dig into the request xml to see what was sent over.
The text was updated successfully, but these errors were encountered: