Select component inside a Repeted Item list

I have a Repeated Items list that has the following items:
One Text Input
One Select Component that gets the data from a collection.

I have an On Change workflow that needs to get the updated content of these two components after edit, but they are not “bindable” it seems. They do not appear anywhere in the binding editor so I can use them in my workflow.
Select components that are placed in an ordinary (not repeat items) container, are available.

I have found the Text element by using a Javascript, but not the result from the Select.

This is the Javascript that works for the Text Input:

const index = context.item.index
const value = context.thisInstance.value

const updated = variables.temp_process_refs.map((row, i) =>
i === index ? { …row, ref_description: value } : row
)

variables.temp_process_refs = […updated]

On Change of the Select does not give me context.item.index or thisinstance.value.

Can anybody help?

Cheers and thanks in advance.

Tom J

Hi Tom!

I think this video might help:

Can you take a look and let me know if you’re still stuck?

Thanks for the tip, Joyce. However… I am using most of the techniques our friend is describing in this video. My issue is different. I find it easy to control each instance in a repeat item list. My problem is how to get hold of the properties for each instance after it has been edited. I.e. the result or value.

In practice, I have an app where the user can edit what i presenetd in the repeated list. As in the Data Grid.
But the content edited by the user, is in a Select component.
So, the list contains n Select components in the list, and in my “Save” workflow, I want to Upsert the choices made by the user. So my plan was to loop through the list and get the selected choice for each row, and upsert accordingly. But the value property (or similar) is not available in the workflow.

I have had to introduce a limitation to my list in order to get this to work. So for the time being, my app has a limitation of ten items in the list, with fixed names, so I can get to the values. (No repeated items).
This is acceptable in practice (this is a cross reference table, where more than ten references will be very rare), but it would have been more elegant to make it fully flexible.

Cheers,
Tom

Hey Tom :waving_hand:

Sorry, I’m struggling a bit to visualize the use case. Would you mind sharing a few screenshots or a video walkthrough?

It’ll help me reproduce the use case on my side and try to find a solution :slight_smile: