nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Report Template Parsing Error for Certain Lines in XLS Form

acanali

I am experiencing a parsing error while loading a report template for particular lines from my XLS form. Everything else loads fine, including previous and subsequent repeats, and other items within the group. I have tried everything and I keep running into the same parsing error. Seems trivial, but I may be overlooking something.

Error: An error occurred when checking the report template. Failed to parse ${samplecollected_yesno | checked:"yes"} since samplecollected_yesno cannot be found in the current parsing scope.

Lines returning an error in XLS form outlined:

XLS form and report template:

Find more posts tagged with

Accepted answers

abureaux

Start with ${#samples2}. It looks to be a repeat. You can’t have a repeat in the middle of a row like that. Needs to be first. EDIT: and in case it wasn’t implied, the repeat also needs to be the last thing in a row.

once you start reformatting that row, you will either fix your problem, or create a new one (not a bad thing - just means start there and see where you end up).

Since you are working on gw, have you done bh yet? I ask because that’s my 2024 goal lol. More precisely, generating XML for importing into Strata.

All comments

abureaux

once you start reformatting that row, you will either fix your problem, or create a new one (not a bad thing - just means start there and see where you end up).

Since you are working on gw, have you done bh yet? I ask because that’s my 2024 goal lol. More precisely, generating XML for importing into Strata.

acanali

Thanks for the response. I ended up reformatting those lines as groups instead of repeats and that seemed to do the trick. In hindsight, I should have considered the effect of nested repeats. Good catch.

A workflow for boreholes logs is also on my list for 2024. I suspect it will be iterative and frustrating. I have seen examples in past using other electronic data collection platforms, so maybe there is hope!

abureaux

"I suspect it will be iterative and frustrating." I suspect truer words have never been spoken lol. This will be an interesting project for sure. Best of luck!

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.