Error Using the Analyze Survey Tool in Survey123 Connect

[AnthonyJonesRSK]

Hi,

Just wondering if anyone else has had issues recently using the Analyze Survey tool in S123 Connect? Both myself and my colleague are getting the error below when running the tool on any new surveys created. This includes just a basic survey with the standard example questions included. On previously created surveys it appears to work fine. We have both had ArcGIS Pro 3.4 installed recently so I wonder if that is causing the issue with the python library. If someone could look into this it would be much appreciated.

Thanks

Anthony

[abureaux]

Any new surveys? Aka, even a new blank survey? If so, call Esri support.

Or only "new" surveys as in the ones you are currently working on? If so, then there could be a few reasons. For example, if you have a calculate with a number in it (e.g., "1", and nothing else), that breaks the Analyze Tool. I would suggest deleting out sections of the survey to find the offending field. It's likely some weird configuration in the survey that the tool is getting hung up on.

[AnthonyJonesRSK]

Yes it's happening with any new survey. Think I will just raise a ticket but just wanted to see if it was something the dev team were aware of. Cheers

[AdministratorWellington_Water]

Yes, I am getting something similar.  We are on Enterprise Portal version 10.9, Survey123 Connect version 3.17 & Arc Pro version 3.3.  

[abureaux]

@AdministratorWellington_Water  In your case, it looks like the XLSX file may be open. The file needs to be closed for the tool to run successfully.

[Richard_Purkis · Accepted solution]

Hi @AnthonyJonesRSK 

Thanks for raising the issue. The upgrade to ArcGIS Pro 3.4 is indeed the cause of the issue. We have logged this as BUG-000173134

A workaround has been identfied:

• In the survey's .xlsx form navigate to the Version tab. Modify the template version from the function to the value of Connect being used. For example, change "=TEXT({3.21}, "0.00")" to "3.21"

Thanks

[AnthonyJonesRSK]

Thanks for looking into this for me Richard, very much appreciated. Can confirm the workaround works for me so I'll mark this as solved now and wait for it to be patched. Cheers