Has anyone had success embedding Sisense dashboards in MS Dynamics 365

Answered

Comments

8 comments

  • Avatar
    Moti Granovsky

    Hi Jane,

    The comment regarding folders is that if your dashboard's URL includes a "folder" parameter, like so:

    http://localhost:8081/app/main#/dashboards/5c0e7055a4ad3144683c7c57?folder=5c18d715a4ad3144683c7c5a

    You should remove this parameter - that is, remove the text:

     folder=5c18d715a4ad3144683c7c5a

    before using this URL to embed the dashboard with an iFrame. You can see this URL when clicking on the share button in the dashboard. If this parameter is not in the URL, no action is required on your side.

    As for the embed parameter - does the dashboard render without it?

    0
    Comment actions Permalink
  • Avatar
    Sisense IFF

    Thanks for clarifying the folder parameter, Moti! Unfortunately the dashboard is not rendering with or without the embed parameter. 

    On the dashboard URL, I am not the dashboard creator  so I do not have the ability to click the share button on the dashboard. I'm using the dashboard URL that presents when I navigate to the dashboard that was shared with me by my colleague who is a Sisense Admin. Would these URLs be the same? Is there anything else we should be trying to troubleshoot?

    Thanks!
    Jane

    0
    Comment actions Permalink
  • Avatar
    Moti Granovsky

    Hi Jane, the URLs should be the same.

    Is your URL in this exact format?

    (either "http" or "https")://(your base URL):(your port)/app/main#/dashboards/(some unique ID)

    Such as:

    http://reporting.motigra.com:8081/app/main#/dashboards/5c0e7055a4ad3144683c7c57

    If it is, when you navigate to this URL in your browser does it load correctly, but won't load in the iFrame? Are you using Internet Explorer, Edge or Firefox? 

    If you are using one of the above browsers and the URL seems correct, try adding a forward slash ( / ) to the URL before the hash sign ( # ), so your URL looks like so:

    http://reporting.motigra.com:8081/app/main/#/dashboards/5c0e7055a4ad3144683c7c57

    If that does not resolve your issue, I'd suggest getting in touch with Sisense support to take a closer look.

    0
    Comment actions Permalink
  • Avatar
    Sisense IFF

    That's Moti. I'll re-reach out to Sisense Support then.

    I'm using Chrome and since we have SSL, the URL does not include the port. We're really trying to make things not dependent on being on our company's internet network.

    When I navigate to the URL in my browser, it loads properly. It's just not loading in the iFrame. I did try adding in the extra forward slash just to see if it would work but it's still not rendering.

    0
    Comment actions Permalink
  • Avatar
    Moti Granovsky

    Hi, since you're using SSL on the port 443, it's just not visible - most browsers hide the default ports (80 and 443) so that's OK, the URL format is still valid without it.

    Since this is the case it seems there are 3 possible causes for your issue I can see, with the last seeming most likely at this point:

    1. Error in the way the iFrame embedding is implemented that we've missed so far
    2. A bug in Sisense
    3. Some sort of incompatibility with Ms Dynamics - possibly them imposing a limitation on iFrames that refer to remote servers (as some sort of XSS protection) or having some other conflict with loading Sisense.

    I would suggest, in parallel to contacting support, to create a simple HTML page with an iFrame and embed Sisense in it the same way, to eliminate the first 2 possibilities, as well as to try and embed another remote website/product in an MS Dynamics view, and lastly - to look for errors in the developer console (by pressing F12 in Chrome) which might indicate what the conflict is.

    0
    Comment actions Permalink
  • Avatar
    Sisense IFF

    Hi Moti, what we've found is that our Sisense Admin can view the embedded dashboard in MS Dynamics 365 but not me (who is just a designer). The majority of our office just have viewer licenses. Does that give you any ideas on possible fixes?

    When I go to the developer console, it does show me a slew of errors along the lines of:

    "main.aspx#748021965:1 Access to XMLHttpRequest at [sanitized]  from origin [sanitized] has been blocked by CORS policy: Request header field LoginRequestCorrelationId is not allowed by Access-Control-Allow-Headers in preflight response."

    0
    Comment actions Permalink
  • Avatar
    Moti Granovsky

    Hi Jane,

    Following up - I understand that the issue was resolved together with Sisense support? Could you share the solution here in case anyone else runs into this in the future?

    Thanks!

    0
    Comment actions Permalink
  • Avatar
    Katie Garrison

    Hi All,

    Based on the ticket description, the issue was caused by an ad blocker. Also, as far as the Microsoft Edge issue we officially do not support Sisense with Edge which is stated in our minimum requirements.

    0
    Comment actions Permalink

Please sign in to leave a comment.