Hi everyone,
Here’s what I’m trying to build in my Tulip App Dashboard (Inside App).
Flow is as followed:
User a date, department, and action (example: Green, Red, etc.), and it stores into a Tulip Table.
- Now, I’m building a dashboard with 31 buttons — each button represents one day of the month (1st, 2nd, 3rd, …, 31st).
- In the dashboard:
- I want to select a Month (e.g., January).
- Based on that selected month, each of the 31 day buttons should change color according to the action stored for that day and department.
In short:
- I want to link each button to its date for the selected month.
- The button color should change based on the action stored for that day and department in the Table.
I’m open for suggestion which will help me achieve to update this particular layout dynamically as soon as the month change and each day is color changed according to its action.
store each date with the action / color in a table and load the color in each button-color-variable.
Also I would consider to save a status as a word or numeric value instead of color (and allocate a color to it) this will make the value available for any other trigger logic (color is not).
This way will also make the data available for future adjustments.
1 Like
As the great @Richard-SNN would say, “Don’t tempt me with a good time!”
Like, Thorsten said, you can do it with a lot of variables and patience. Make sure to use many triggers instead of many blocks for easy copy and pasting.
But as the great @giladl would say, “Is the juice worth the squeeze?”
This is overhead that your team will have to maintain in perpetuity. This exact same output could absolutely just be done in more of a table format, and with some analytics you could probably still find some fun and colorful ways to share the data.
1 Like
Hi
How about making a table that holds a column for each day? Then you need only load one record to make the visualization
Then you insert Table Records on the step and show each column as its own Table record widget. The widget is entirely filled with the color when displayed.
You can then either have your transparent grid on top or the table record widget , or put the Table record on top of your diagram (which is why I stored slightly transparent colors).
I am suggesting this only because in my experience running 30+ triggers carries an step overhead. If the data could be prepared in advance (perhaps by Automations adjusting/creating a row for each department) then it will load real fast.
We used this trick in some overview steps where the color was shown and we placed a transparent button on top. That would indicate to the user that something needed to be taken care of without having to wait 10+ seconds for the step to do all the trigger logic.
1 Like
