List multi-selection input
This guide will take you through how to set up a list multi-selection input.
Prerequisite data
No connectors will be used in this example, but data from table steps will be utilized. Please download the file below; it will be used to import into the required table steps
Add a list multi-selection input
Open an existing application or create a new one in an application package and open it in the Designer.
Add a User step.
Add a Table step.
Open the Table step and select Import File.
Choose the semicolon separator and click OK.
Select the "List selection.csv" file downloaded in the prerequisite section above.
Set the table variable name to "Articles" and click OK.
Change the step name to "Articles". It's good practice to name steps after their content.
Right-click on the "Articles" step, select Add data arrow, and connect it to the User step created in step 1.
Open the User step.
Add a List multi-selection input.
In the Target Variable, write "articles".
Under Data Source, in Table Variable, choose the table "Articles".
Set the Default Selection to "{Name = "Small box"}".
Under Appearance, in Prompt, write "Choose an article".
In Large Row Text, write "{Name}".
In Small Row Text, write "{Cost}{" in SEK"}".
Le the Group Rows By be none.
Click the Play button in the top right-hand corner to run the application in diagnostic mode.
Add configuration
When working with tables, connect offers a variety of possibilities to add configuration and style to make it look more suiting for your purpose.
Go back to the Designer.
Open the drop-down in Group Rows By and choose "Cost".
Run the application in diagnostic mode again.
You can also display this grouping with colors.
Remove "Cost" from Group Rows By.
In the Item Style, open the editor by clicking the arrows to the far right.
Add the code below.
Click the Play button in the top right-hand corner to run the application in diagnostic mode.
Condition to hide
In the Condition To Hide, write “{userId = “your user id”} (the user Id you log in to Connect with)
Run the application in diagnostic mode again.
Last updated