Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
See why IDC MarketScape names Qlik a 2025 Leader! Read more
cancel
Showing results for 
Search instead for 
Did you mean: 
karolina_
Creator II
Creator II

Section Access - question from quiz

Hi All,

I'm doing quiz from qlik.com website and I got stuck on one question.

Which of the following is true about Section Access tables? 

A. The number of user security records is limited to one million   - it is not, although there is limitation for reduction field(s) that cannot handle more than 1M unique values (Section Access limitation of 1M rows?)

B. All Section Access tables must be defined in the Hidden Script - not a must, a good practise

C. You can only perform data reduction on a single field          - no, u can have more than 1

D. All field names and values are automatically converted to upper case  - only in inline load or text file load (When does Section Access "ACCESS" field value require upper case ?). From QV 11 reference manual "All the fields listed in Load or Select statements in the section access must be written in UPPER CASE. Any field name containing lower case letters in the database should be converted to upper case using the upper function, see upper(textexpression) (page 320), before being read by the Load or Select statement."

E. Don't know - fits best for me now

Help & explanation appreciated

11 Replies
Not applicable

I can confirm - an extract from my QV Developer book (from the classroom course) states:

All field names and values are converted to Uppercase in the SECTION ACCESS. Use the UPPER function to convert the field values to UPPERCASE.

Bill_Britt
Former Employee
Former Employee

HI,

That is only taking about inline loads..

**Note that all data loaded via an external data source must be loaded in upper case

in the SECTION ACCESS statement. This does not apply to INLINE data which always

will be treated as upper case.

Bill - Principal Technical Support Engineer at Qlik
To help users find verified answers, please don't forget to use the "Accept as Solution" button on any posts that helped you resolve your problem or question.