This article contains the gotchas and best practices of what to think of when integrating Sense into Sharepoint - and to some extent other portals.
This article is for anyone who wants to integrate a Qlik Sense component into Sharepoint (or any other similar portal). The integrator should have the following knowledge:
The following is needed for the example in this article to work (if you are a very proficient Sense user, the following doesn't differ from a normal quick setup of Qlik Sense):
Recommended settings on the Qlik Sense environment The recommended settings can be summed up as follows: don't touch the default settings (besides the 3rd party certificate if root certificate isn't trusted on every client machine; see below for comment) after installation if you want to make it easy for yourself.If you need to modify the default settings or want more than surface knowledge of settings relevant for this article, you can see the items below:
Step by step walkthrough
Integrating a Sense object into a Sharepoint page is very simple and with default settings of an installation (as mentioned above) you only need to do the following:
Note: A QlikView webpart already exists. No Sharepoint webpart exists today for Sense. We have for now decided that it isn't really needed, since it is easy enough to add an <iframe> to a Sharepoint page and referencing whatever part of Sense you want and it will work! Still, there could be a need for a webpart to make non-technical people able to add parts of Sense to Sharepoint by just making choices in drop-down menues in Sharepoint.
Creating this webpart and making it user-friendly with contextual drop-downs would require some integration work on the Sharepoint side: