Office Hours Reschedule
Hi all
,
Flo and I are away today, so Office Hours will be postponed this week.
If anyone was planning on bringing any questions, feel free to post them in this thread ![]()
Office Hours Reschedule
Hi all
,
Flo and I are away today, so Office Hours will be postponed this week.
If anyone was planning on bringing any questions, feel free to post them in this thread ![]()
Hi @Matthew_S , I was thinking of attending to ask about this supabase file loading issue. I posted it on the forum.
Hi @emdiemeric , I answered your thread, can you try to see if my solution helped you?
Hi @Matthew_S !
Need help with component logic.
When I trigger the workflow externally it executes only in the first instance of the component (first item of the repeating items list)
How to reset all component variables inside all instances?
Hereās a video with demonstration: Resetting Data in Repeating Components: A Workflow Challenge | Loom
I tried to write a JS loop using my component UID and with
wwLib.getFrontDocument().querySelectorAll('[data-ww-uid="c7015eaf-a266-4fc5-9da9-1851353cf279"][class$="ww-flexbox__object"]');
By this I was able to fetch all intsances with ids.
But I couldnāt find a way to set a right context from those objects to execute context.component.methods.executeWorkflow
And as I found in old messages from @aurelie using object uids is not the right thing to do.
I would recommend using an āInitial valueā for this kind of dynamic repeating of inputs. You might need to adjust the current setup a bit, but it will make the resetting much more straightforward: https://screen.studio/share/RLpJX9hw?state=uploading
big thanks for the quick response!
I shouldāve shown you the whole idea. Sorry I didnāt do it right away.
One more attempt with my question, if you allow: Optimizing Filter Setup for Multiple Entities in My Model š” | Loom
What I want to achieve - I want to use a component variable binded to āinitial valueā as a proxy just to always show the default option in a dropdown when itās been resetted.
I can bind āinit valueā to the filter schema JSON object (something like "schema.filter_type.current_filter.option[0]"), but this will lead to the facts that:
It will require making sure that in each filter the first element is always the default option (āoption[0]ā). And this is doable, so itās fine.
It will add more complexity to the setup when I need to reset any dropdown to default option. By resetting component variable itās pretty simple. By resetting the whole schema JSON object its much more complicated in terms of configuring right paths.
UPDATE:
- It will require making sure that in each filter the first element is always the default option (āoption[0]ā). And this is doable, so itās fine.
I tested it. This is not gonna work, because init value would be āhardcodedā and wouldnāt change. So no reset will be applied.
Unfortunately the expected behaviour for using component actions on a repeating list of components is as you are experiencing ā it will only execute on one of them. There isnāt yet the functionality to target an instance in a repeating list for component actions, so to handle this you would need to use features in the component configuration.
I think you get the gist of how you would need to set up the underlying data to support it, but just as an example: Arc ā Screen Studio
Thank you very much, Matthew!
Iāll do some workaround as you proposed.
Meanwhile I found this video https://www.youtube.com/watch?v=NL99k69Mo74&t=1189s
and it was pretty insightful ![]()