Skip to main content
Announcements
See what Drew Clarke has to say about the Qlik Talend Cloud launch! READ THE BLOG
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

UPPERCASE Field Names in Section Access

Hi,

After going through number of articles, we found that, for section access script, we need the field names to be in Upper Case.

In our application, all the fields are in lower case.

Is there is any quick tip so that, we can handle the uppercase part in Section access script.

Please assist.

Regards,

MK

5 Replies
alexandros17
Partner - Champion III
Partner - Champion III

Unfortunately no ...

giakoum
Partner - Master II
Partner - Master II

if you don't want to change case for your fields, create a copy column of the field you need to apply section access on, with the same name, just in uppercase :

For example :

field, value:

DimensionID, 1

DimensionName, Europe

DIMENSIONNAME, EUROPE

hide it to avoid confusion for the user

tracysmart
Creator II
Creator II

you will need to wrap them with UPPER but I don't think there is a quick way to do this other than typing that out in the script.

morganaaron
Specialist
Specialist

There's no "quick" answer here - unless you change the fields in your app to uppercase on your load by using the Upper() function.

Alternate ways to handle this are to create bridging tables using an inline load or loading your field values to a fieldname that's ignored like %NAME if you use the hide prefix command for % signs, and then you could read your values in as Upper() as %NAME and your linking field along with this to create the bridge to your section access format.

Colin-Albert

Load the field a second time e.g. of the filed you want to select in section access is company_name

Then use something like

     load

     company_name,

     upper(company_name) as COMPANY_NAME_SA,

     ...

Your existing charts will work with the company_name field, and you can implement section access using the COMPANY_NAME_SA field. This makes your data model a bit bigger dues to the duplicate fields, but avoids the need to rebuild all your charts and other objects etc.