Skip to main content

Suggest an Idea

Vote for your favorite Qlik product ideas and add your own suggestions.

Announcements
Have questions about Qlik Connect? Join us live on April 10th, at 11 AM ET: SIGN UP NOW

Web Connectors - Office 365 Sharepoint Connector - SiteUsers table - subsite path feature

JesseRajala
Partner - Contributor II
Partner - Contributor II

Web Connectors - Office 365 Sharepoint Connector - SiteUsers table - subsite path feature

Attachments

The Office 365 Sharepoint Connector functionality for pulling data from the SiteUsers table needs a subsite path parameter, like found in searches for several other Sharepoint tables. As the SiteUsers are specific to a site (including sub-sites), there is no functionality to get the list of users for a specific sub-site. It can be accomplished by adding the site to the Base URL, but as the same web connector is used for several site searches, this breaks the search.

We are extracting list data from Sharepoint generated by a PowerApp, and the list entry contains a field OwnerID. In Qlik, we also need the OwnerName field, which in this case can be derived from the SiteUsers table. However, due to the site-specific of site-users, the current functionality for the O365 Sharepoint Connector only fetches SiteUser data for the root Sharepoint site (Base URL), not any specific subsite, so the match based on OwnerId is wrong. These subsites can not be defined in the connection string either.

5 Comments
chrisbrain
Partner - Specialist II
Partner - Specialist II

Hi - Thanks for reporting this. So just to clarify:

  • You have verified that when you include the subsite after the base URL you get the correct list of users for that subsite?
  • You would like to see subsite added as a proper table parameter for the SiteUsers table so that you can modify this as needed for each request to the connector?
JesseRajala
Partner - Contributor II
Partner - Contributor II

Hi,

Yes to both questions.

When I add 'sites/Example' to the Base URL, the Data previewed and fetched is for the correct site/subsite. This means I can use the SiteUsers for one-off manual fetches from certain subsites, but can not automate it, as the Base URL needs to point to the root for other reloads to function properly. There also seems to be now possibility to refer/alter to the Base URL within Qlik script, which would have enabled changing the Base URL for different reloads with a dynamic variable.

If possible, I would like a proper table parameter for 'Subsite path' where the site/subsite can be given separate to the Base URL, as can be found in several other table search functions (e.g. ListItemsFromID). I also tried to amend the connection string [used in Qlik script] with &subsite=sites%2fExample but it had no effect on the outcome.

I posted two images as attachments, but they aren't showing for me at least at the moment, so I'll post the other one again for clarity:

If the SiteUsers table could have a similar parameter for Sub site path, this would work perfect.

JesseRajala_1-1601296506018.png

 

chrisbrain
Partner - Specialist II
Partner - Specialist II

Thanks - we are looking at adding this.

It looks like what you are entering is actually a site collection rather than a subsite. The reason I say this is that when I initially started testing this with only different subsites, the API which this table uses actually always returns the same list of users but if you enter a different site (i.e. site collection) you do actually get the users.

I will see if we can clarify this in the UI.

b_garside
Partner - Specialist
Partner - Specialist

A new connector should be native in QS like it is for PowerBI and Tableau. Many customers choose alternatives because QS does not natively support this data source. And lets be honest his connector isnt exactly friendly to use or made for the masses.

P-O_Davidson
Employee
Employee

The Site/Subsite Path parameter was added to the SiteUsers table in a release during the fall 2020.

Status changed to: Closed - Already Available