However, if I attempt to load the data into a separate external table, and then load that table to handle section access it doesn’t recognize the user ID, and I get locked out of the application.
The same issue happens regardless if I load the source table as inline, or from another source table. I have a large number of users to create, and it makes a lot more sense to load them from a source table, but this issue is preventing it. I’ve done this successfully in the past using NT type section access, which is running successfully in 10. So I’m not sure what’s up.
I understand this is old thread but I thought I'll contribute my understanding...
You need to make the Reduction field and Section Access Fields in UPPER CASE (Field Values). Although, if you are using INLINE Load then QlikView implicitly converts them to UPPER CASE. But if you are loading from Excel / Databases / Other Sources/ Resident Load/ QVD Load then you need to make the field values to UPPER CASE.
As suggested by Michael Steedle it works fine when you change the field values to UPPER Case. I don't think it's a bug and infact it is right behaviour because your INLINE table still holds the Case Type (UPPER or lower) based on what you type. However, only when you load the Section Access table as INLINE Load then it will implicity convert the field values in UPPER case. It completely makes sense to me because whenever you are typing the values in INLINE Load for Section Access and if it doesn't work after typing because it's in lower case then it is very frustrating for the Developer. So QlikTech provided this implicit Case Conversion for Section Access but it still hold original Case Type outside Section Access.
Bottom line: As a thumb rule always do UPPER case wherever you are loading Section Access script and if you are using INLINE Load then you don't have to worry about changing the field values to UPPER case...anyway you can't do that as well!
