topic Survey 123 Report Template Error: Failed to parse/does not exist or cannot be found in current parsing scope. in ArcGIS Survey123 Questions

Survey 123 Report Template Error: Failed to parse/does not exist or cannot be found in current parsing scope.

ChrisShuck — Fri, 01 Mar 2019 23:47:01 GMT

I am trying to upload a report template to Survey123 however I keep getting the error Failed to parse "${MT_Amount1} Field "${MT_Amount1}" does not exist or cannot be found in current parsing scope.

I have checked the XLS spreadsheet in Connect to make sure that the tag matched exactly, and to my knowledge the opening and closing tags for the repeat is placed correctly as well

Is there an update that could be causing this? It was working fine a few weeks ago with the same tags and the same survey.

Re: Survey 123 Report Template Error: Failed to parse/does not exist or cannot be found in current parsing scope.

ChrisShuck — Sun, 03 Mar 2019 01:29:33 GMT

This error has appeared on 5 or 6 of my company's surveys. All of these began just after the 3.3 release on 2/26. In each survey, there is a random field that receives this error. Prior to the appearance of these errors, reports for all of these surveys had been generating without issue. No changes were made by us. The only common factor that I can see for the fields mentioned in the error messages is that they are fields within repeats. I published a copy of one of these surveys, but the problem persisted. I also tried removing the tag that was prompting the error. After that, I received the error message for the next field within that repeat. It did not give an error for the very first field in the repeat.

Re: Survey 123 Report Template Error: Failed to parse/does not exist or cannot be found in current parsing scope.

ChrisShuck — Sun, 03 Mar 2019 03:13:12 GMT

UPDATE: The problem has been solved. If the repeat name is MT, the field name cannot start with MT as in MT_Amount1. When all field names that started in that manner were edited, with those letters being removed, I was able to successfully generate reports. I'm sure this is related to the 3.3 update. Can anyone explain why it might be incorrect to start a field name with the same letters as the repeat name?

Re: Survey 123 Report Template Error: Failed to parse/does not exist or cannot be found in current parsing scope.

JamesTedrick — Sun, 03 Mar 2019 04:45:14 GMT

Hi Chris,

This was a bug discovered late in release testing, related to an enhancement introduced to specify a field by using <tablename>.<fieldname> (this was introduced to enable referencing a field in the parent table inside a repeat section). We will be addressing this issue in the near future.

Re: Survey 123 Report Template Error: Failed to parse/does not exist or cannot be found in current parsing scope.

ChrisShuck — Sun, 03 Mar 2019 05:19:10 GMT

Thanks for your response. Do you have an estimated time frame? I'm trying to decide if I should go ahead and fix our surveys now, which will be quite time consuming, or wait on ESRI's fix. We rely heavily on those surveys and need them up and running as soon as possible.

Thanks,

Chris

Re: Survey 123 Report Template Error: Failed to parse/does not exist or cannot be found in current parsing scope.

Anonymous User — Mon, 04 Mar 2019 03:19:33 GMT

Hi Chris,

The fix for this issue should be applied to the website by the end of next week (hopefully around 14/15th March) but due to testing and release certification could vary slightly. We will keep you updated once available. If you can wait I would suggest that is the best option, as other changes you make as a workaround may require changes to question names/fields or repeat names, which will change the schema of your survey and could result in data loss.

Phil.

Re: Survey 123 Report Template Error: Failed to parse/does not exist or cannot be found in current parsing scope.

ChrisShuck — Mon, 04 Mar 2019 17:39:39 GMT

Hi Phillip,

Thanks for providing the timeline.

-Chris

Re: Survey 123 Report Template Error: Failed to parse/does not exist or cannot be found in current parsing scope.

ZachPearo — Thu, 28 Mar 2019 18:08:14 GMT

Hi, I am having the same issue. Is there a new time frame with regards to this fix?

Thank you,

Zach

Re: Survey 123 Report Template Error: Failed to parse/does not exist or cannot be found in current parsing scope.

Anonymous User — Thu, 28 Mar 2019 21:45:21 GMT

Hi Zach,

This issue has already been resolved on the website and verified as fixed. If you are still encountering an issues the cause could be different. Can you please provide more details of the issue or a copy of your xlsx form and custom report to be able to reproduce?

Phil.

Re: Survey 123 Report Template Error: Failed to parse/does not exist or cannot be found in current parsing scope.

ZachPearo — Mon, 01 Apr 2019 14:26:34 GMT

Hi Phil,

Thank you for reaching out. I’ve attached a copy of my Survey Form as well as my Word Template. Could the issue be that I want to autopopulate the header?

Thank you,

Zach

Re: Survey 123 Report Template Error: Failed to parse/does not exist or cannot be found in current parsing scope.

Anonymous User — Tue, 02 Apr 2019 03:45:27 GMT

Thanks, I will take a look and get back to you soon. Phil.

Re: Survey 123 Report Template Error: Failed to parse/does not exist or cannot be found in current parsing scope.

ZachPearo — Tue, 02 Apr 2019 04:21:13 GMT

I figured it out Phil. Thank you! Not sure how it worked, but I switched “propertyname” to “ “landname” in the form and then in the template and created a new survey and it worked.

Zach Pearo

Conservation Easement Steward

Society for the Protection of NH Forests

54 Portsmouth St, Concord, NH 03301

zpearo@forestsociety.org

Office: 603.224.9945 x338

Cell: 603.400.2190

Re: Survey 123 Report Template Error: Failed to parse/does not exist or cannot be found in current parsing scope.

Anonymous User — Tue, 02 Apr 2019 04:48:55 GMT

Hi Zach,

Thanks for letting me know, I have reached out to one of our website developers to check about the use of "propertyname" as a field name and if we would expect any issues in the feature report. It appears it could be causing an error when the report runs. Using a different name for that question would be the correct workaround for now.

Phil.

Re: Survey 123 Report Template Error: Failed to parse/does not exist or cannot be found in current parsing scope.

ZhifangWang — Wed, 03 Apr 2019 03:46:56 GMT

Hi Zach,

Thanks for sharing the template with us.

Actually, the "propertyname" should work in the template. If you check the header of the second page in the report template, there's a placeholder ${propetyname} which has a typo (missing an "r"). The "propertyname" issue will be gone once you fix this typo.

Thanks,

Zhifang

Re: Survey 123 Report Template Error: Failed to parse/does not exist or cannot be found in current parsing scope.

ZachPearo — Wed, 03 Apr 2019 19:08:51 GMT

Of course it was that easy! I’ll keep it the way I have it as it doesn’t make a difference at this point. Thank you for notifying me of this though, it’s nice to know that I’m not crazy, just bad at spelling.

Re: Survey 123 Report Template Error: Failed to parse/does not exist or cannot be found in current parsing scope.

Anonymous User — Wed, 03 Apr 2019 19:32:45 GMT

Hello,

I have been in the process of creating and fine tuning a series of custom reports for this year's survey season this week. I have noticed a change in something that I find important for the reporting process while using custom reports. I have found that now there is no opportunity to pull a value from a question that is located "outside" of the repeat.

Meaning, I have a survey that contains a question named "Unique_ID" to be used in documenting a "Unique ID" for the survey. I then have a repeat that contains a series of questions that pertain to sampling events that occur at this location. Within my custom report I was able to call the "Unique_ID" question into the repeat to be used within generating the "Unique ID" for each sampling event. However, it appears there is now a validation process that is running to check for all fields within the repeat prior to allowing the custom report to be uploaded. My repeat does not contain the "Unique_ID" question within it and I am receiving an error upon uploading the custom report. The error is "Error: Failed to parse "${QuestionNameOutsideRepeat}". Field "${QuestionNameOutsideRepeat}" does not exist or cannot be found in current parsing scope."

The only way for me to get around this is to add in a new question "Unique_ID_Temp" into the repeat and pass the value from the "Unique_ID" question outside of the repeat into this new field through a calculation. This is causing a bloat within my database as I was able to use fields outside of the repeat, but now I have to create temp fields to house this information. I use to call multiple fields such as the Unique ID, Latitude, Longitude, and a few others into the repeat for use in reporting efforts, but that is no longer available.

I am using the ${RepeatName} ${/RepeatName} tags within my custom report to access all of the related records for the primary survey.

Are there any other workarounds for this? Any insight would be greatly appreciated.

Thank you,

Mike

Re: Survey 123 Report Template Error: Failed to parse/does not exist or cannot be found in current parsing scope.

ZachPearo — Wed, 03 Apr 2019 19:37:39 GMT

Can you post your word template document and excel form like I did above? Esri staff may ask you to do this as well so I may be saving you a bit of time.

Re: Survey 123 Report Template Error: Failed to parse/does not exist or cannot be found in current parsing scope.

Anonymous User — Wed, 03 Apr 2019 19:42:31 GMT

Hey Zach, I have been through both with a fine tooth comb and I know it is not due to a miss-spelling and I can confirm that this field is not found within the actual "repeat" (related table) for the survey. So, I think what I might try is something that James referenced above about being able to reference questions from the parent survey into the repeat.

James stated: "This was a bug discovered late in release testing, related to an enhancement introduced to specify a field by using <tablename>.<fieldname> (this was introduced to enable referencing a field in the parent table inside a repeat section). We will be addressing this issue in the near future."

I am going to give this a try first to see if this works, but thank you for the tips.

Re: Survey 123 Report Template Error: Failed to parse/does not exist or cannot be found in current parsing scope.

ZachPearo — Wed, 03 Apr 2019 19:50:02 GMT

Hi Mike,

I just created a new survey recently and am able to access information outside of the repeat. Download my form and template that I previously posted above and see if that helps. I made a little mistake, simply missing one letter in a header on the 2nd page.

Re: Survey 123 Report Template Error: Failed to parse/does not exist or cannot be found in current parsing scope.

Anonymous User — Wed, 03 Apr 2019 20:05:53 GMT

Hey Zach,

Within my custom report the field is pulling fine when it is not within the repeat, but once it is located inside of the repeat, then it bombs out.

Outside repeat

Inside repeat

James/Brandon, could you give me a little more insight on this referencing of the parent field into the repeat? My parent is named "Acoustic_Bat_Detector" and the field that I want to call into the repeat is "DetectorID".

I have tried without any luck?

${#BatDtctrInfo} Acoustic_Bat_Detector.${DetectorID}

${#BatDtctrInfo} <Acoustic_Bat_Detector>.${DetectorID}

${#BatDtctrInfo} Acoustic_Bat_Detector.${DetectorID}

Thank you in advance,

Mike