Nested Repeats - Accessing Outer Repeat Values in Inner Repeat

Wappler General
1

I have two nested repeat regions, accessing server connect data from outer and inner. The data available from these server connects is:

outer.data.outer.id
outer.data.outer.outer_name

inner.data.inner.id
inner.data.inner.outer_id
inner.data.inner.inner_name

I have my nested repeat like this:

dmx-repeat:r_outer="outer.data.outer"
   dmx-repeat:r_inner="inner.data.inner.where(`outer_id`, "**OUTER_ID**", "==") "
      <p>{{**OUTER_ID**}}</p>
      <p>{{outer_name}}</p>
      <p>{{id}}</p>
      <p>{{inner_name}}</p>

What do I put for **OUTER_ID** to get the value of outer.data.outer.id?

2

Are these repeats nested in the server action as explained here?

Or if not, how are they nested/related?

3

No, they are not nested at all in the server connect. They are two totally separate server actions.

One fetches the data only for outer, and one fetches the data only for inner.

I guess I forgot to say that inner also has a field containing the id of outer! I’ll add that to the post…

4

So how are they related / how do you nest them? Is every parent repeating all the children or are they filtered somehow?

5

They are filtered with a .where(). I’ll add that to the syntax above…

6

So can’t you just select the parent repeat id in the picker, the same way you selected it for the where filter?
I can see it works perfectly fine:

Screenshot_15
Screenshot_15591×863 78 KB

7

Correct, I can’t.

For some reason, my parent repeat is not showing any of the values that can be selected! :frowning:

Could you just tell me the syntax please?

8

Well, it’s just {{BindingName}}

9

So in my example above, is it just {{id}}?

In which case, is there any syntax to differentiate the id value of outer from the id value of inner?

Or should I just edit the server action and rename the id value of outer to be outer_id?

10

@Teodor, do you have an answer to my question above? :slight_smile:

11

Well I believe I answered your question :slight_smile:

12

Best is to have different names, it will use the first binding it finds with the given name, starting with the scope it is called from and going up until it finds the binding.

You could try with {{parent.id}} or {{parent.parent.id}}, but this doesn’t work always and can break if you wrap your html differently.

1 Like
13

Thank you Patrick!