how to add a trigger on single select control?
adding a Trigger on a Single Select is not currently possible, although you can either:
- place a Trigger on a timer and check for the change of the Single Select
- add a button that checks for the value of the Single Select
alternatively, if you add an Interactive Table, you can place a Trigger on value change on that widget.
could you describe a little more of the use case and what you’re trying to achieve?? thanks again for posting!!
actually I am using single select control within my application and on its selection I want to add its value in tulip table .
So how can we do this?
OK, thanks for clarifying @suvarnap
to do that you will need to create a Table Record Placeholder and add a Button that 1. Creates a Table Record (if it’s not already loaded into the Table Record Placeholder) and 2. Data Manipulation > Store the Variable into the Table Record field:
does that make sense?? this Support Article has some useful information to achieve exactly what you’re describing: How To Modify Tables Within the App Editor | Tulip Help Center - Support for Building Manufacturing Apps
let us know if you have further questions.
Thanks for your response but I don’t want to use button to save value in tulip table.
Is there any alternate option?
Option on Sigle select to have sometnihg similar to “Row selected” trigger on Interactive table control would be nice. That way I can use it to load record and dispay aditional data of selected ID to app user.
hello @ermingut, I agree with you that this would be a useful feature that would streamline App building.
do you think you could submit suggestion in Product suggestions - Tulip Community, so our Product team can track this and ask further details on your suggestion if necessary?? let me know if you have any questions!!
@ermingut @suvarnap One alternative to using the Single Select widget I’ve found is to use an embedded Tulip Table to achieve a similar result (as alluded to by the row selected trigger). You can set up the table to follow some hierarchical structure like what I’ve done here:
In the app, you can setup an embedded Table to use a default filter to only return the highest level choices. Then, when you click on a row, you can determine if the row you’re selecting has sub-items, and change the filter, essentially repopulating the embedded table.