Display of field_names in status_box

[datanibbler]

Hi,

we have a number of fields which, in the underlying DataModel, are qualified with the table_name.

- In a multi_selection_box we have on many charts, an alias_name can be assigned to a field

<=> In a status_box (which we have underneath that on most charts), the original fieldname is used. That, however, is

just too long and the available space in that status_box is quickly used up.

=> Can I somehow set the fields to be displayed (so I cannot use HidePrefix), but with an alias_name?

Thanks a lot!

Best regards,

DataNibbler

[Anonymous]

Pardon me if I have not understood your issue.

When you say a status box, Do mean a current selection box? If Yes, I am sure you cannot have an alias shown there.

Let me know if you mean otherwise.

Regards,

Aadil

[datanibbler]

Hi Aadil,

you are exactly right. I mean a "current selections"-box.

It's a pity that I can't do that - just having the field_names displayed without the table_name would shorten it significantly - and also make it much more meaningful - just having the table_name with three dots displayed because the status_box isn't broad enough to accommodate the entire name is not very helpful at all...

Best regards,

DataNibbler

[#4]

DataNibbler ... you do know you can make the field wider in the Current Selections box ?

[Anonymous]

Agree with you, Totally.

I would always try to alias the field names at the end of the script to the required names. If you have lots of fields, I would suggest you try the FieldMap option and alias the fields name, at least the ones that are used in your dimensions.

[datanibbler]

Hi Aadil,

what option is that? I couldn't find it in the help file

@ Parminder

Yes, I know - but I cannot make the fields so big that they could accommodate a fully qualified fieldname 😉

Best regards,

DataNibbler

[Anonymous · Accepted solution]

here it is..

Rename Field

Renames one or more existing QlikView field(s) after they have been loaded.

Two differently named fields cannot be renamed to having the same name. The script will run without errors, but the second field will not be renamed.

The syntax is:

rename field (using mapname | oldname to newname{ , oldname to newname })

rename fields (using mapname | oldname to newname{ , oldname to newname })

where:

mapname is the name of a previously loaded mapping table containing one or more pairs of old and new field names.

oldname is the old field name .

newname is the new field name.

Either syntax: rename field or rename fields can be used.

Examples:

Rename field XAZ0007 to Sales;

FieldMap:

Mapping SQL SELECT oldnames, newnames FROM datadictionary;

Rename fields using FieldMap;

Regards,

Aadil

[#8]

The table name will be what you decide to call it before the load comand.

Is there a reason you don't use a more presentable name in the Load script ?

[datanibbler]

Hi,

@ Parminder

that particular app has been created by a colleague, I don't want to mess with it too much.

Moreover, the fields come from a QlikMart - a DataModel that we load previously and which is in turn loaded in a BINARY LOAD into the individual apps.

@ Aadil

Can you tell me what would happen if I were to use that in different tables and fields get the same new_name? Will those then be linked by QlikView? I wouldn't want that - that's part of the reason why we qualify fieldnames in the first place...

[#10]

If you have two fields with the same exact name , qlikview will make a join , unless they have been qualified.

I would recommend you get  the Qlikmart amended to have more concise table names.

Otherwise you have to repeat this process everytime you use it.