Skip to content

Quick Links

My Account
Welcome Guest
Knowledge

It is requested to to allow Qlik Sense to read a QVW with section access and NTNAME

Article Number: 000084088 | Last Modified: 2019/09/24

Description

It is requested to to allow Qlik Sense to read a QVW with section access and NTNAME

It is not currently possible to binary load a QVW with section access into Qlik Sense, which reduces reusability. QlikView requires NTNAME, Qlik Sense requires USERID, and if USERID is simply added to the section access table that QlikView is looking at, QlikView no longer opens the document on the server.
 

Environment:

  • Qlik Sense Enterprise June 2019
  • QlikView April 2019

Cause

Working as designed. Unfortunately, there is no support for common section access between QlikView and Qlik sense when it comes to the USERID field. This is a known limitation due to the fact that USERID is implemented differently between QlikView and Qlik Sense. This means that the section access table does not translate very well between the two clients and is best kept as separate tables for the two clients.

Feature Request ID:
  • 1791 - Section Access compatibility between QlikView and Qlik Sense

Resolution

Workaround:

  1. One current solution is to keep two QVWs; one for QlikView and one for Qlik Sense.
! Qlik has previously received feedback on this feature and recorded the request for future review.  For up to date information and to express you would like the Feature implemented please contact support at support.qlik.com referencing this article. 
 


Get Answers

Find Answers

Qlik Community

Collaborate with over 60,000 Qlik technologists and members around the world to get answers to your questions, and maximize success.

Join Us
Get Support

Have a Question?

Search Qlik's Support Knowledge database or request assisted support for highly complex issues.

Submit a case
Talk with a Representative

Critical Issues

Experiencing a serious issue, please contact us by phone. For Data Integration related issues please refer to your onboarding documentation for current phone number.

Call Us