#4318 - Fanatical Zendesk Dashboard Error
We updated our sub-domain name on 1/31; we have also updated our Zendesk configuration in Admin to the new sub-domain name.
Cases are being created in Sugar, but our Fanatical Zendesk dashboard displays this error: "We did not receive a response in the 200 range. Code received: 404 Response: { "error": { "title": "No help desk at brainselltechnologies.zendesk.com", "message": "There is no help desk configured at this address. This means that the address is available and that you can claim it at http://www.zendesk.com/signup" } } Note: brainselltechnologies.zendesk.com is the old sub-domain - the new one is configured.
Please advise how I can resolve this issue. Thanks!
4 years ago
Thanks for reaching out. To confirm, it sounds like you re-connected to Zendesk using Step 3 of the Zendesk Configuration tool, is that correct? Can you walk through the steps below and tell me what appears?
Please let me know if you have any trouble with the steps above.
Best, Heidi
4 years ago
Hello Heidi - WOW, thanks for the speedy reply. I tried to attach a pdf - but got an error message that the file type cannot be uploaded??? Anyway, the result for zendesk-default-subdomain is "brainselltechnologies" - which is contrary to our current correct sub-domain
4 years ago
Happy to help. It looks like we need to change a configuration which governs the subdomain the integration is referencing. Can you follow the same steps to enter this into the Console (replaced the end value from newsubdomaingoeshere to the new subdomain you're using):
SUGAR.App.api.call('create',SUGAR.App.api.buildURL('FanaticalZendesk/setting/zendesk_default_subdomain'),{key:'zendesk_default_subdomain',value:'newsubdomaingoeshere'},{})
From there, re-connect again from Step 3 of the Zendesk Configuration page and let me know if you still have trouble.
Thanks, Heidi
4 years ago
Hello - thank you for the reply - I will implement these changes 2/10 evening and will let you know how it goes! Thanks!
4 years ago
BTW - can you please post what you mean "Step 3 of the Zendesk Configuration tool" ?? Just want to confirm we are totally on the same page... thanks!
4 years ago
Hello Heidi - I am having issues with getting the console to cooperate - these are the steps I am using, as you stated above:
Error message is: "Uncaught ReferenceError: SUGAR is not defined at :1:1 (anonymous) @ VM980:1
Why can't I add a pdf file??? I can't see t o add any file - please doublecheck your copied link and get back to me... thanks!
4 years ago
Happy to help. Yes, you'll reconnect by clicking Step 3 (the Connect step) of Zendesk configuration, as shown here: https://d.pr/i/xIvHab
In regards to the error you're getting, can you confirm that the drop-down under the Console tab reads "top" as shown here: https://d.pr/i/JFaq1e ?
If so, can you send a screenshot of what you're encountering to zendesk@fanaticallabs.com so I can take a closer look?
Thanks, Heidi
4 years ago
Hi Heidi - yes, console says "top" -- but I am accessing through Zendesk - not Sugar - which is exactly what I did the first time .... I will send you a screen shot to the email address - thanks!
4 years ago
Hi Heidi - I will access Sugar CRM Admin and will share the results with you.
4 years ago
Apologies for the confusion! Yes, these steps are done within Sugar. I'll modify the steps below to indicate this:
That should take care of the issue you're encountering but let me know if it doesn't. If needed, you can also schedule a time to walk through these steps together using the link below:
https://calendly.com/fanaticallabs_support/fanatically-zen-support-meeting">Schedule a Support Meeting
Best, Heidi
4 years ago
Hello Heidi - I was successful BUT I cannot edit the existing Dashboard. Same results - nothing has changed.... clearly, I need to get on the phone with support. How do I arrange an actual phone call?
4 years ago
Sorry you're still having trouble! I'm happy to chat. You can schedule a call using this link: https://calendly.com/fanaticallabs_support/fanatically-zen-support-meeting
Thanks, Heidi