Open jcguyette opened 6 years ago
i got the same problem. Did you get it resolved?
Eventually, yes. It appears that if there were any errant field entries - for us, it was incorrect data present in the Domain field - the tool was not able to contend with those entries and triggered the error reported.
Once I went through all of the organizations and removed the faulty data present, I was able to continue use of the tool. It's obviously a bit limited in its error checking, and the pagination aspect of it was less than desirable, but overall, we were able to utilize it to remove the rest of the organizations needed.
It certainly would be nice of Zendesk offered a robust native functionality to do so directly within the UI, right?
Hi both,
Thanks for your discussion here, and sorry for not getting around to your original comment @jcguyette. I'll take a look at this shortly.
Can I ask you to clarify on how the data was incorrect or faulty in your case?
For us, the "faulty" data was a result of the integration we had in place between Zendesk and Salesforce. The previous integration was configured to ensure that nothing from Salesforce came over to Zendesk because SF was a mess and ZD was tightly controlled and a mess.
Sometime along this year that integration configuration was modified and we ended up with data flowing to ZD from SF. With that incoming data came the new Organizations that were created in SF, and with those unwanted/inaccurate Organizations came data that was stored in SF and was somehow mapped to the Domains field in the Zendesk Organization fields.
It is that data in the Domains field that we found was faulty. Instead of only including content such as "gmail.com, ymail.com, outlook.com, such-and-such-university.edu", there were entire paragraphs of text that would not be considered to be properly formatted for that field.
It was that mess of data within the Domains field that I had to remove before I could run the Bult Delete utility, as it seemed to be failing on that field. However, as there was no log for me to determine exactly where/how/why it was failing, this is only a guess. The removal of the data from the Domains field appears to have led to the tool working again... but it could have been coincidental.
Hope that helps.
Thanks for that info @jcguyette! In attempting to replicate the behaviour, I find that I can't update an org with this type of information in the domains field. Anything which does not match the domain format is rejected, whether I try from the UI, Salesforce integration, or directly with a REST API call. I receive a 422 Unprocessable Entity and the update is not saved. Perhaps it's a gap that has since been closed, but it looks like I can't reproduce it any more.
@jcguyette and @ajones1983: if you are still seeing the error can you email support@zendesk.com with the details? You can let them know I asked you to write in, and they can assign the ticket to me.
After removing approximately 200 unwanted organizations, we have been encountering the following error:
"Uh oh, looks like something went wrong. Please try again, or report an error if the issue persists."