Skip to main content Skip to complementary content

listbox properties

listbox()

These are the properties used by Qlik Sense list boxes.

Since:
  • Qlik Sense November 2017

When the engine calculates the layout of a list object, it calculates all values. If some selections are applied, the selected values are displayed along with the excluded and optional values

Properties

showTitles

Type: Boolean

Show title for the visualization.

Default: true.

showDetails

Type: Boolean

Sets if visualization details should be shown.

Default: false

title

Type: String | qStringExpression

Visualization title shown if "showTitles": true.

subtitle

Type: String | qStringExpression

Visualization subtitle shown if "showTitles": true.

footnote

Type: String | qStringExpression

Visualization footnote shown if "showTitles": true.

disableNavMenu

Type: Boolean

Disables the hover menu in the visualization.

Default: false

qListObjectDef

Type: Object

A subset of the properties available in the ListObjectDef is presented here. For complete documentation of all available properties, see Engine API: ListObjectDef.

Properties

  • qDef

    Type: Object

    Description: Extends NxInlineDimensionDef, see Engine API: NxInlineDimensionDef.

    qDef properties
    Name Type Description
    autoSort Boolean

    Set to automatically sort the dimension.

    Default: true

    cId String ID used by the client. Must be unique within the current chart.
    othersLabel StringExpressionContainer String expression container.

  • frequencyEnabled

    Type: Boolean

    Controls whether or not the frequency count is displayed in the listbox. Default: false

Examples using qlik-visual

Tip noteFor more examples of how to create list boxes on the fly, see Mashups: Creating list boxes.

In this example we create a basic list box with a custom title.

<qlik-visual appid="Tutorial-Golf.qvf"
  type="listbox"
  cols='["Course"]'
  options='{
    "showTitles": true,
    "title": "Courses"
  }' >
</qlik-visual>

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!