Fields organization

[#1]

First of all I'm brain new in using QV.

I'm impressed of QV capabilities even if I would share some "enhancement" with you.

I'm used to work with Business Objects and, one of the most import feature, I'm used to create a report starting from an ORGANIZED LIST OF CATEGORIZED AND STRUCTURED LIST OF FILEDS ( UNIVERSE )

( example of BO Universe )

As you can see it is extremely helpfull for users to find a filed.

If you are interested in a customer filed you have just to expand the Customer tree and select it.

Now I know that one of the worst case, approaching new prodcuts, is trying to use same way of working and thinking

But I also believe that the experience must be used to enhance the quality of working.

So, a part from if I didn't find another and existing way to organize filed differently, I'm wondering what do you think about it.

[prasad]

Hi,

You can do grouping in many ways, once loaded data, create different sheets with particular requirement and add the dimensions and fields required for that purpose. You can create many sheets to support the user requirement. The data gets loaded each time you refresh the file.

Prasad

[Anonymous]

To see the "universe" of the logical tables ("categories") and fields, press CTRL+T on the keyboard.

[#4]

If I understood well you are referring to script developpment while I'm referring to field selection.

I mean, once created the LOAD script, when I add a working object on my desk, selecting a field I see a long list of LOADEd field in a sorted list without a logical organization.

[#5]

It seams that QV is a technicle-user oriented and not just a end-user oriented.

When a business-user works, needs to be supported by a simplified-clear-business-language proposing organised business-categorized trees

When adding an object the list of field is prompted in a alphabetic order ?! ...

[Anonymous]

I'm referring to the data model viewing that you get after script development, not to the script development itself. It is extremely helpful for front end objects design.
BTW, you can always see the list of fields for a single logical table. As a rule, when you create an object, and have the list of fields (yes, in alphabetic order), there is is a drop-down just below the list where you can select a single logical table - your field list will show the fields only for the selected table.

As for "QV is a technicle-user oriented and not just a end-user oriented" - it depends on the user level of QV knowledge.

[#7]

Ok found.

Better than nothing ( actually they can be seen by table )

But as I posted a discussion-post I also would like to get some impression on my considerations.

What do you think about having a selection-area organized by categorized fields, as I shown in my first post ?

Are you aware of it and what is your opinion ?

[#8]

quote "What do you think about having a selection-area organized by categorized fields, as I shown in my first post ?"

I think this can be created on a single sheet in the QlikView document by using a set of List Boxes. By analysing the data you have loaded you should be able to work out which fields you need to display, and how to link them to create categories to give a multi-level selection.

Of course this is not the best way, as putting the List Boxes on the same sheet as the charts, etc. is a better way for users to make selections.

[Anonymous]

If you think this feature is needed, you can submit a feature request to QlikTech - see above. They listen.
It may help users who come from the different BI products.