Dimensions
This section describes how the different dimensions work and the configuration options available to each of them.
Readonly
ReadonlyDescription: A non-editable text input that can be used to present a value directly from a Qlik Field
To be sure not to have any conflicts with Qlik's data load, try to avoid special characters such as '/' or '<>' in your Komment Key Fields
Display as URL:
For Readonly widgets it is possible to choose to display the content as a clickable URL.
In the Komment table the user will be able to click on the URL which will open up in a new tab:
Text
TextDescription: Plain text input, mainly for free text.
Options:
Choose between a single line or multiple line display
Ability to limit the maximum number of characters a user can write
Date
DateDescription: A date picker to easily select a date from a calendar view
Options:
Select via a calendar view
Type date directly in widget
Define the format in which the date should be displayed
Dropdown
DropdownDescription: A drop-down menu with configurable options as input data
Options:
Define possible values manually
Load possible values from Qlik data field or variable (e.g. use the concat function like this in the Options field:
Concat(distinct [First Name],';'))Enable a search option for the users
Enable users to add their own options in case the possible ones are not sufficient
Allow for the selection of multiple values
Group Button
Group ButtonDescription: Similar to the Select option but renders the options as grouped buttons
Options:
Define possible values manually
Load possible values from Qlik data field or variable (e.g. use the concat function like this in the Options field:
Concat(distinct [First Name],';'))Define colors for each button
Number
NumberDescription: A numeric input field formatted as a number
Options:
Define Number Type. Can be set to either Number or Percentage
Define number of Decimals to be included
Enter number directly in input field
Toggle number up and down directly in widget
Check
CheckDescription: Works as a check box to easily indicate e.g. completion of a task
Validation expression
Validation expressionDescription: This feature can be applied to any dimension. Use this for any conditional checks before saving the input. A validation expression is required here to check if the input data is fulfilling requirements and limits. Check the other dimension’s content by evaluating the binding variables in each widget.
Options:
Define exact expression to be used for a given validation step - e.g. only allow for 1 record to be saved each time.
Define the desired message the user should be presented with when the validation expression is not met.
2.1 Add dimensions
2.2 Define dimensions
Dimension Type: Select your dimension type.
Fiel: Select the relevant field name from the defined Fact Table.
Komment Key Field: If your selected field is the association between your data model and write-back data then check this field.
Label: Define the label for the dimension. If nothing is entered the Field Name will be displayed.
Continue this for all the dimensions you want to add.
We recommend to place the dimension holding the Komment Key Field as the first dimension.
3. Finalize configuration
3.1 Preview Load Script
Go to Shortcuts => Press Preview Load Script
3.2 Initialize Data Model
You will now be presented with the auto-generated Komment load script as shown below.
Now press Initialize Data Model. Komment will now automatically inject the script in your Data Load Editor and do a reload of the application.
That's it! You have now successfully configured your write-back solution.
3.3 External script
If you want to externalize the Komment script section and use variable based path, you must ensure that the variable is not cleared out after must_include/include function:
//Set script path
LET vScriptPath = ‘lib://myScriptFolder’;
//Include komment logic in qvs file
$(Must_Include=[$(vScriptPath)/Writebacks/Komment.qvs]);
//Clean variables
LET vScriptPath = ‘’;In above case, Qlik will run into an error when reloading. That’s because Qlik will firstly execute the ‘Clean variables’ part rather than ‘Include’ function. So the suggestion is to either move the clean logic into a qvs with include or remove it if not necessary.
Last updated