Result of nested repeats in feature report templates as table

CSDING_GIS

Hi All,

I have got a form with a nested repeat, whose results i would like to display in a table, but i cant get the feature report template to work. I would like for a user to be able to choose a category and then add as many pendencies and according due dates as they like. My feature report should then show the topic in the left cell and add new lines in column 2 & 3 of the feasture report according to the specifications done in the form.

Example:

Topic	Pendencies	Due date	Action reauired?
A	Pendency a1	asap	no
	Pendency a2	31.12.2020
B	Pendency b1	asap	yes
C	Pendency C1	today	yes
	Pendency C2	2020
	Pendency C3	2030

Here's my code for the xlsx form...

type	name	label
begin repeat	entries
select_one topic	topic	Topic
begin repeat	pendencies	Pendencies
text	pendency	Pendency
text	due_date	Due Date:
end repeat
select_one yes_no	action	Action required?
end repeat

and the feature report template:

Topic	Pendencies	Due date	Action reauired?
${#entries}${topic}	${#pendencies}${pendency}	${due_date}${/}	${action}${/}

When i upload the feature report template to Survey123 online, i get the error message: "Failed to parse ${action}. Field ${action} does not exist or cannot be found in current parsing scope.". I think thats due to the fact that my nested repeat is spread over two columns. Is there any way to solve this problem? Would greatly appreciate someone's help on this.

Thanks,

Flo

#nested repeat‌ #feature report template‌

BarbaraWebster1

Hi Flo,

You should be able to fix the error message if you use the following syntax for showing the nested repeats in a table:

Topic	Pendencies	Action required?	Due date
${#entries}${#pendencies}${entries.topic}	${pendency}	${due_date}${/}	${entries.action}${/}

More info on this can be found in the repeats section of the Feature report templates documentation.

It isn’t possible to display multiple repeat rows next to a single adjacent parent row, but if you include the repeat on a different line, you can get a similar effect. See example below.

Topic	Pendencies	Action required?	Due date
${#entries} ${topic}			${entries.action}
	${#pendencies}${pendency}	${due_date}${/}	${/}

-Barbara