
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Qlik Sense SaaS Share Point connectivity
Looking for advice on what could be the issue re: Qlik Sense in the cloud connecting to a share point folder.
The connection get a "Connection succeeded" result for the connection test however when the little pencil is used to locate locate the file to load it into the script, an error message “An error occurred while parsing EntityName” pops up and we are not able to proceed.
I have read that an "&" does not work and was wondering if this could be the issue because the Space has an "&" in the name.
I have attached a screen shot here.
Accepted Solutions

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello @njmaehler ,
The connection details should look something similar to this:
Base url:
https://test.sharepoint.com/
Site/Subsite path:
/sites/testsite/
When creating the connection, the connector checks the connectivity against the Base URL but doesn't check the site/subsite access permissions that why it's possible to create a connection.
We would suggest creating a feature request to improve the test connection.
Best regards,
Francisco

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I changed the space name however I am still getting the same error.
Something to note is that the Sharepoint name is registered with "(Pty) Ltd" in the name and possibly the brackets are the issue. I did see a similar issue in QlikView years back hence the reason I am mentioning this.
The problem will be that the client is not able to change that company name so I would need a work around if this is a possible cause.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello @njmaehler ,
The connection details should look something similar to this:
Base url:
https://test.sharepoint.com/
Site/Subsite path:
/sites/testsite/
When creating the connection, the connector checks the connectivity against the Base URL but doesn't check the site/subsite access permissions that why it's possible to create a connection.
We would suggest creating a feature request to improve the test connection.
Best regards,
Francisco
