Share
Report
40Since June 11 we get next error when updating an incoming E-mail: "The specified contact doesn't belong to the account selected as the customer. Specify a contact that belongs to the selected account, and then try again."
This is the train of events:
1. an incoming mail is receieved from a watchdog service i.e. Kaseya
2. An incident is automaticly created from the E-mail. The E-mailaddress of that Kaseya service is linked to the account of our company. So the incident is created with our company is customer and the Kasey contact as contact.
3. The account on the incident is manually changed to the appropiate account
4. The contact on the incident is manually changed to the appropiate contact (or removed)
We have a custom field on the E-mail entity to monitor if the E-mail is read. Upon opening the E-mail form, a JavaScript makes a request to the Web API to modify this custom field. At this point we get the above mentioned error.
We first noticed it on June 11, for 2 days before it never happened (before June 9 we didn't have this error)
Strangly enough we don't get this error in our development environment which is a copy of the production environment from approximatly 3 weeks ago. I made a new copy of the production environment and the errors occur there.
Is there a way to bypass this check or is there another way to modify custom fields on these E-mails?
All responses (
Answers (
