# Error when using trigger within repeat groups

**URL:** <https://forum.getodk.org/t/error-when-using-trigger-within-repeat-groups/54348>\
**Category:** Support\
**Created:** [March 28, 2025, 10:57am UTC](https://forum.getodk.org/t/error-when-using-trigger-within-repeat-groups/54348 "2025-03-28T10:57:05Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![wroos](https://getodk.b-cdn.net/letter_avatar_proxy/v4/letter/w/77aa72/32.png) [@wroos](https://forum.getodk.org/u/wroos)\
**Post date:** [March 29, 2025, 10:08pm UTC](https://forum.getodk.org/t/error-when-using-trigger-within-repeat-groups/54348/4 "2025-03-29T22:08:28Z")

</div>

For anonymization, we used another approach, also inside repeats:  
The name field(s) have a **relevant** clause: ${SetAnonym} != "OK":  
(based on acknowledge type SetAnonym variable, required, at the end).

An advantage might be that only on save the name fields are emptied. So an erroneous tick could still be corrected before.

But your trigger example needs further examination, e.g. by @LN or @Xiphware, please.

**See** also a similar problem reported in the past [Incorrect (setvalue) trigger behavior in Enketo when used inside repeats - #6 by LN](https://forum.getodk.org/t/incorrect-setvalue-trigger-behavior-in-enketo-when-used-inside-repeats/49058/6).

---

_[View the full topic](https://forum.getodk.org/t/error-when-using-trigger-within-repeat-groups/54348)._
