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.
I am having the same issue as LocationDataServ. There are no repeats other than for the photos and the exact field names are in the templates. I get a 'could not find ${field} in parsing scope' or '${field} is not defined. This only happens on certain reports, which doesn't make sense because I use the same template for the reports that do successfully run. We need these reports for our clients and I cannot find another workaround other than to try and export them to .docx, which works intermittently. Please advise.
I'm getting the same error. If I delete the offending field from the template, the error just moves on to the next field. All fields are within the repeat table. This is by far the simplest template I'm attempting to publish, so I'd like to get this issues resolved before driving myself crazy with the others.
Hi There, I receive the same error when I upload a custom report template into Survey123 , please see error below:
I have no repeats in my form and my field names are exactly the same in my report template as they are in my form/feature service.
My report template is very simple and just contains a table within a summary. When I do not include the summary within the report, I do not receive the error but when I do include the summary I receive the error.
Am I missing something? Have I not included the summary notation correctly?
Please find attached a copy of the excel form and the word report template.
Any help would be greatly appreciated!
Thanks!
Siona
James,
I am getting this error when trying to run a custom feature report from a hosted AGOL survey and I'm officially stumped: Failed to parse ${ if[object Object]}
Attached is my template and my survey xls. Thank you so much.
Hi Reuben,
Just to confirm, this is a duplicate post with https://community.esri.com/message/952395-re-survey123-feature-report-failed-to-parse?commentID=952395, correct?
Having an issue with failed to parse inside a repeat, Attached screen shot shows the field ${testNo} as a valid Field name code but error message tells me otherwise. Any help appreciated, thanks.
I checked your .xlsx and it looks like you have field_26 then it jumps to field_42, you may want to download the sample data from the form-software and relink your fields.
I hope that helps!
I am having the same error. Any help would be appreciated!!! I've uploaded the form, template , and error message.
Hi Michelle,
Good to hear it works. We will keep eyes on the issue you mentioned. If you encounter the issue again, feel free to leave us a comment.
Jiateng
It did work two days before.
I rebuilt the Word document and it's working again.
Hi Michelle and Robin,
Does the template work before Jan 29 or 30? If it is possible could you please provide us more information related to your issue? For example, a copy of your xlsx form and report template would help us to reproduce the issue. If you are not able to share these files, could you tell us more about the condition?
Thanks a lot!
I'm having the same problem but with the ${select_one | selected:"yes"}Yes format. Started for me yesterday.
I got his error this morning, has something changed online in the last two days?
Hi Liz,
Seems your issue is similar to the BUG-000125687. Can you please upload a screenshot of the modify schema dialog (Publish->Modify schema) which scrolls to the question "Funder"? This helps us to confirm if it's the same issue with the above bug.
Although we fixed the bug and will auto-truncate names for any choice which is longer than 32 characters, there is a chance that a longer than 32 character name is input manually in the modify schema dialog. In this way, we won't change it until you manually fix it.
Thanks,
Zhifang
Thank you for the suggestion. I cleared browser cache, no change.
I made a copy of the survey; same issue occurred. So I tried deleting that question that was triggering the "error" and when tried saving/previewing/publishing it displayed the same error message, this time pointing to a different question, which also has not been edited/changed in anyway since last editing/publishing successfully. Any other recommendations? Is this just a bug?
Thank you very much for your time.
Liz
First could I ask you to clear your browser cache and attempt to publish again?
If you still see this issue, could you try the 'Save As' option to make a copy of the survey and try to publish that?
Hello,
I'm experiencing this error now, even though this survey was created in June after this bug was apparently fixed based on what I've read above.
I went in to add a choice to a different question than the one that is producing the error; so no changes were made to the question that seems to be the issue. Since the error does not allow me to publish, I cannot view the schema to see if there is an issue there with a duplicate value.
Please see screenshot, and please advise on how to resolve this issue. I logged out and logged back in, and waited a few days to see if the bug resolved itself; but it has not.
Thank you,
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.
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.
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.
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.
Mike
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.
Chris
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.
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?
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.
Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
.png)
