Skip to main content

Hello 

 

We are looking to implement Embedded chat on a local site so that we can test out a new MIAW implementation. 

I have provided the code snippet from the Embedded Chat Deployment to our front end team (which works successfully when internally testing in the pre-provided visualforce test page) but on trying to initiate the chat from external test site, they are receiving an error as follows: 

 

[EmbeddedServiceBootstrap] Attempted to initialize bootstrap multiple times

 oa @ bootstrap.min.js:28

 h @ bootstrap.min.js:30

 (anonymous) @ bootstrap.min.js:182

 initEmbeddedMessaging @ webchat.html:11

 onclick @ webchat.html:28

 

I am looking for just a bit of guidance where I may point my web team to troubleshoot this issue.  Is this error message a "common" thing that might point to salesforce config.  Or would it be more a front end technical error. 

 

Really just looking for guidance or where I might look to troubleshoot this issue when I don't know about front end stuff and they don't know about Salesforce.  Any help appreciated! Thanks 

 

Niall 

 

 

 

#Service Cloud

6 respostas
  1. 25 de ago., 21:02

    Hi @Kamlesh Regar

     

     

    Checking back through our documentation - I can see that we did receive the same error you have detailed. However, we were receiving the error 100% of the time - though you have reported to be inconsistent, so I am not sure if the same issue will resolve. 

     

    We made 2 changes at the same time and resolved the error so I also could not be confident if 1 of these changes would have resolved or it needed both changes. 

     

    Change 1

     

    We had originally added the salesforce provided script in the head tag instead of the body tag.  The script has now been moved into the body tag. 

     

    Change 2 

    We needed to add the site domain into the "Trusted URL" option within setup menu.  After adding the URL, it was essential that we needed to set the "frame-src" checkbox option to "true"   

    Hi Checking back through our documentation - I can see that we did receive the same error you have detailed. 

    I am not very confident in this area of front end setup, so I really hope this can help solve your issue!

0/9000