Hi,
is it possible to change the backgroundcolor of a list-item (or another element) within a workflow?
I tried with AI, but without result.
(In my project I want to change the backgroundcolor of a list-item when it is clicked)
Nice solution, never thought to do it this way.
Thanks !
Hi @Batik_Okazov,
in a new project I am using a formula in the (backgrond-)color property that checks if a certain value exist in a column of my connected Baserow-API. (red if exists, gray if not exists).
In my case : if the value doesn’t exist when opening that page, the background-color is grey (= Correct), but when I add the value with a workflow (so the value then exists in the Baserow-field), the color stays red in stead of “automatically” changing to red.
Even after a “fetch collection” at the end of the workflow, the field still has the (old - initial) gray background instead of the (expected) red color.
So it seems that the “fetch collection” flow doesn’t activate the formula in the color-parameter.
Any idea how to solve?
I tried with a variable to change the background-color, but then all the items have the new background-color, not the one I wanted.
The first screenshot shows the list of items with the initial red background if name exist in field.
In the second screenshot there’s the formula for the color-element
The third screenshot shows part of the workflow where the new name is added to Baserow (GET API - works fine) and the “fetch-collection”-action (that doesn’t give me the updated result)
If - after the workflow - I go back to previous screen (navigate in the app) and reopen the detail-screen, I see the correct color for the added name.
So the problem is in the “realtime-update” from Baserow.
Hi Wim,
when you make REST API call to save new data in Baserow are you sure you correctly update your ‘gekozen_repetitiedatum.OPT_namen_NEE’ variable after the ‘fetch collection’?
Because ‘fetch collection’ action updates the ‘repetities’ collection only and does not update your custom ‘gekozen_repetitiedatum.OPT_namen_NEE’ variable.
I assume you have an old data inside the variable and that’s why it doesn’t update reactively, but updates only on page load. Maybe you set your variable only on page load event.
Thanks for the suggestion, but how do I (only) update ‘gekozen_repetitiedatum.OPT_namen_NEE’ after the fetch? OPT_namen_NEE is not a custom weweb-variable but a field (column) in my Baserow-table ‘repetities’ (where I save the changes with a REST API)
26 aug. 2026 18:35:24 Batik_Okazov <notifications@weweb.discoursemail.com>:
“filterByKey” formula needs an array as the first argument. So your gekozen_repetitiedatum should be a variable with an array inside, otherwise the formula wouldn’t work.
Since the formula works you must be placing your collection data inside gekozen_repetitiedatum var. You just need to update array inside gekozen_repetitiedatum right after collection fetch.
Can you confirm or elaborate on what exactly gekozen_repetitiedatum is if it’s not a variable?
Thanks to your tips, I’ve taken a thorough look at both the workflow and the variables.
In a separate post (Store array with one object into an object-variable - #5 by WimDC), I reported the issue with the object variable, and a solution was then found.
This was only possible thanks to your initial help.
So the problem is now sorted – thank you very much!