topic Re: Qlik Sense in Sharepoint in Integration, Extension & APIs

Qlik Sense in Sharepoint

Emmanuel_DORR — Mon, 09 Sep 2024 09:20:36 GMT

Hello,

I'm using Qlik Sense client managed and i try to integrate a specific sheet in my sharepoint site. to do that, I added a specific virtual proxy that I configured with SameSite attribute to "none".

About the integration in sharepoint, I use an IFRAME Web part.

It workd but i notice that the simple fact of opening my sheet in sharepoint consumes 5 sessions at the same time. So, when I try to open my QS app diresctly on the hub, I get the message "Too many sessions active in parallel".

Why does sharepoint open so many sessions to simply display a Qlik Sense sheet in an IFRAME?

How can I fix this issue ?

Thanks,

Emmanuel

Re: Qlik Sense in Sharepoint

jprdonnelly — Fri, 13 Sep 2024 16:49:13 GMT

@Emmanuel_DORR ,

Do you mean the "Embed</>" webpart, or are you referring to a legacy, client-managed, Sharepoint instance?

If the latter, I think there may be issues with the part not caching session data/cookies properly.

Re: Qlik Sense in Sharepoint

David_Friend — Fri, 13 Sep 2024 17:40:53 GMT

proxy looks configured correctly according to: https://community.qlik.com/t5/Official-Support-Articles/Missing-SameSite-attribute-blocks-requests-in-Chrome-80-and/ta-p/1712551 (which you followed)

What browser is this in? Version of Sense?

Re: Qlik Sense in Sharepoint

Emmanuel_DORR — Mon, 16 Sep 2024 06:39:00 GMT

--> Qlik Sense February 2024 Patch 5 (Update 1)

--> Browser Google Chrome

This doesn't seem to happen systematically.

Re: Qlik Sense in Sharepoint

Emmanuel_DORR — Mon, 16 Sep 2024 06:39:46 GMT

Yes i'm using the embedded webpart :

Re: Qlik Sense in Sharepoint

jprdonnelly — Mon, 16 Sep 2024 15:08:52 GMT

@Emmanuel_DORR - thank you for the update. Also, ARGH!

If this is the only embed part on the page, from no existing Sense sessions being active, it is hard to explain. The one thing I would suggest at this point is to investigate using the Identity parameter, this way you should at least able to programmatically isolate the embedded session from any others active on the platform.