I am trying to implement a filter expression for my embedded repeat. However, it looks like there are problems finding the field.
The following example works, i.e. the UI-Preview loads.
This example does not.
The error message for the second example is the same as if I would enter a gibberish field name, giving me the impression that if a field is located in a subfolder, there are problems with referencing the field in this filter expression.
I need to reference the field in my second example for my filter expression. How do I do this?
Hi @jasper-silent-root,
The Documentation for these filters explains that:
Example for group scope for an enumeration field with the name “NumberEnum” defined in the group “MyFieldGroup”:
kontext(MyFieldGroup) { [NumberEnum] } = "THREE"
In the first example, your field Steuernummer_GINSTER is directly in the repeatable group. In the second example, you have modeled the field in a group (Bescheid). Does the following expression work?
kontext(Bescheid) { [KeineEinzelBekanntgabe] } = "false"
Yes, this worked. Thank you!
My UI starts with your expression, but the moment I try to enter anything into the table, I get the following error message.
Hey @jasper-silent-root,
I could reproduce your issue and see the use case, that you want to structure your document model with groups. I would also interpret the docu in that way that it should work. Hence, I would suggest writing a ticket for this.
A workaround could be a helper field within your repeatable group FB (so not nested the sub-group Bescheid), that is filled by a computation rule with the value of your subordinate field. Or to dissolve the subordinate group Bescheid.
(However, the preview works correctly if the subordinate group is repeatable. (So if Bescheid would be repeatable, your filter expression would work correctly and according to the docu.) If you use the subgroup just in order to structure your DM or it comes from an include and is not repeatable, the error is thrown.)
Update: @felix-blazing-river has created the ticket A12-14657 to follow up on this. Thank you!
Update: The issue is fixed in 2023.06-ext3.
