# Entities in Repeat Groups

**URL:** <https://forum.getodk.org/t/entities-in-repeat-groups/54509>\
**Category:** Support\
**Tags:** entities\
**Created:** [April 11, 2025, 8:20pm UTC](https://forum.getodk.org/t/entities-in-repeat-groups/54509 "2025-04-11T20:20:06Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Emalee\_Martin](https://getodk.b-cdn.net/user_avatar/forum.getodk.org/emalee_martin/32/27055_2.png) [@Emalee\_Martin](https://forum.getodk.org/u/Emalee_Martin)\
**Post date:** [April 11, 2025, 8:20pm UTC](https://forum.getodk.org/t/entities-in-repeat-groups/54509/1 "2025-04-11T20:20:06Z")

</div>

I am trying to connect two forms using entities. The first form collects household data then uses a repeat to collect individual information for each household member present. Each household member is assigned a barcode (this occurs inside the repeat). I am trying to use entities here to connect the household form to the test results form. However, when uploading the form to ODK I got the error "The XLSForm could not be converted: [row : 28] Currently, you can't create entities from repeats. You may only specify save\_to values for form fields outside of repeats."

Is there a work around here? I am trying to avoid creating an additional form.

Thanks in advance!  
Emalee

---

<div class="post-metadata">

**Author:** ![ktuite](https://getodk.b-cdn.net/user_avatar/forum.getodk.org/ktuite/32/14766_2.png) [@ktuite](https://forum.getodk.org/u/ktuite)\
**Post date:** [April 14, 2025, 6:55pm UTC](https://forum.getodk.org/t/entities-in-repeat-groups/54509/2 "2025-04-14T18:55:31Z")

</div>

Hi @Emalee_Martin,

We are currently planning out how to add entities from repeats to support your exact scenario, but it won't be available for several months.

As a temporary workaround, is there a maximum number of household members you usually expect? Could you not use a repeat and basically "unroll" or manually copy what would otherwise be in the repeat by referring to specific numbered members? `member_01_barcode` ... `member_10_barcode`? You could use a `relevant` command to only show the next member if the previous one was filled in and it was less than the number of household members? Sorry, this isn't a very elegant solution! But maybe something like this will work for you until we can build support for entities from repeats.

| type | name | label | hint | required | constraint | relevant |
| --- | --- | --- | --- | --- | --- | --- |
| text | household\_id | Household ID | | yes | | |
| integer | num\_members | Number of household members | | yes | . \> 0 | |
| note | member\_note | Now we'll collect information for each member | | | | |
| Member 1 | | | | | | |
| text | member1\_name | Name (Member 1) | | yes | | ${num\_members} \>= 1 |
| select\_one gender | member1\_gender | Gender (Member 1) | | yes | | ${num\_members} \>= 1 |
| integer | member1\_age | Age (Member 1) | | yes | . \> 0 | ${num\_members} \>= 1 |
| barcode | member1\_barcode | Scan barcode for Member 1 | | yes | | ${num\_members} \>= 1 |
| Member 2 | | | | | | |
| text | member2\_name | Name (Member 2) | | yes | | ${num\_members} \>= 2 |
| select\_one gender | member2\_gender | Gender (Member 2) | | yes | | ${num\_members} \>= 2 |
| integer | member2\_age | Age (Member 2) | | yes | . \> 0 | ${num\_members} \>= 2 |
| barcode | member2\_barcode | Scan barcode for Member 2 | | yes | | ${num\_members} \>= 2 |
| Member 3 (and so on...) | | | | | | |
| text | member3\_name | Name (Member 3) | | yes | | ${num\_members} \>= 3 |
| select\_one gender | member3\_gender | Gender (Member 3) | | yes | | ${num\_members} \>= 3 |
| integer | member3\_age | Age (Member 3) | | yes | . \> 0 | ${num\_members} \>= 3 |
| barcode | member3\_barcode | Scan barcode for Member 3 | | yes | | ${num\_members} \>= 3 |