TRUECHART Knowledge Base Live Search
With version 1.4.x of the menubar comes a bunch of new features. Here is a short introduction to the main features of this release.
New name and logo
The extension got renamed and is now called menubar. With the new name the menubar also got a brand new logo.
Figure 2. New menubar logo.
The Field Slider allows to select values of a dimension with a slider component.
Figure 3. Field Slider examples.
Dynamic font sizing
The option to set the font size dynamically allows for responsive font sizing depending on the width of the extension object.
Hide elements in Sense mobile view
Now you can hide menubar elements when Qlik Sense is in mobile mode. Just activate the checkbox in the property panel and the element is not active in Sense mobile mode. Inactive elements dont trigger any actions or behaviors such as the default selections.
Individual colors for all elements
Individual colors can be defined for every element of the menubar. There is no limitation on what you want to style. Even the funkiest menubars can now be designed.
Figure 4. Individual Colors.
Option to style sheet background
The option to style the sheet background allows you to style the Sense sheet background with an image, color or both. This also works in storymode if a menubar elements is placed on the slide and has an active background styling.
Figure 5. Sheet with Background styling.
For more information about the changes in this version, refer to the chapter menubar v1.4.1
An upgrade from version less than v1.1.0 to the current version may require an migration. If this migration is not done carefully, apps may break. The procedure is described in detail in Migration from version less v1.1.0..
Migration for published apps
In the context of new versions, necessary adjustments within the apps are usually carried out automatically during loading. This is transparent for the users. An indication of this are corresponding logging entries in the development console of the browser.
Since changes to published apps cannot be saved, these automatic changes must be made at every load, which can have a negative effect on the loading speed of the visualization.
To avoid permanent migrations of the apps, we therefore recommend opening the corresponding apps as soon as possible in an unpublished mode, so that migration is then performed once and the changes are saved automatically. These apps should then be published again.
Migration from version less v1.1.0
With the release of version v1.1.0 we introduced the support of master and dynamic dimensions. To use this feature, you have to be sure that all expressions correspond to the expression syntax known from Qlik Sense, which means:
"before and after field or dimension names
Expressions should begin with
Correct spelling (upper-/lowercase) of field or dimension names
After updating, menubar will guide you through this process. At first, navigate to the sheets where you use menubar. Now, it will automaticly check if you use expressions somewhere. If so, you will see the dialog below. Please make sure that all expressions comply with the above mentioned specifications. Once you have done this, you can confirm by clicking on the appropriate button. Only when all expressions have been confirmed, you are able to save the changes and close the dialog.
Figure 6. The dialog that leads you trough the migration process
Automatic migration for published apps in production
Changes to a published app cannot be persisted. So it is necessary to perform the migration in another way:
Figure 7. Process to migrate published apps
Install the new menubar version in your testing environment.
Now open all relevant apps. Check and confirm all expressions. But you will not be able to perform the save operation.
menubar.zipand copy the content of all apps from the Config settings dialog in between the curly brackets at expressionMigration. Make sure that the existing format is maintained.
Finally, zip the complete
menubardirectory and upload the ZIP file to the Qlik Management Console on the production environment. For all expressions in the config file you will not be asked to reconfirm them.
When you are using menubar in a publicated app or in mutiple apps with the same expressions, we recommend to update the
config.js. The advantage of this variant is that expressions added in the config file do not have to be reconfirmed.
For published apps, this is the only way to persist changes on the expressions.
An update to the latest version of the menubar without prior adjustment of the dimension expressions leads to incorrect evaluation of the dimensions and therefore corrupt published apps!
Figure 8. The Config settings dialog