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; } } }

Survey 123 form Error: Initializing form... Error: not a object

PaulSweeney3

Hi All

See screen shot below that is appearing intermittently across our forms emebedded in dashboards

the same dashboards were working fine a few days ago and no changes have been made to either the form or dashboard. it only occurs when the form is opened in edit mode. the globalid is present in the feature layer also .

Trouver plus de publications taguées avec

Accepted answers

SteveMartin__MDTA_

I think I figured it out. Check the settings for the embedded object. For me, I had it set to latest. I went back and changed it to my current version of Survey123 Connect which is 3.14. I reloaded the page and it works fine now.

All comments

EricaNova

I'm still currently experiencing this issue. Adding the ?version=3.21 to the end of the URL worked for the form, but not for editing data. Thoughts?

ZhifangWang

Hi @ANRGIS ,

Did the "out of memory" issue occur before this fix? If it occurs consistently, can you please share the XLSForm file with me via a direct message?

ANRGIS

I went back to my original calculations and it works. Thanks.

Now the only issue is the "out of memory" browser error every once in awhile. Hmmm

ZhifangWang

Hello everyone,

The fix for this issue was deployed to the Survey123 website earlier today. Original surveys affected by the issue should now work automatically.

Thank you again for your feedback.

ANRGIS

@JackFanZhang,

Unfortunately I already published with 3.22 (current version) and I believe older Connect version are not available.

JackFanZhang

New issue to me. Seems new version of web form has introduced some bug that can't be handled by the old template. Originally I had it set to always use the latest version in Survey123 Survey setting. Fixed by change it back to use the version published with.

ZhifangWang

Hi @ChessClaire ,

This issue exists in the survey itself so you can test by directly opening it in the Survey123 web app https://survey123.arcgis.com/share/<surveyItemId>.

On the other hand, you can load the survey using the Survey123 beta web app in the widget of Experience Builder app by setting URL parameter https://experience.arcgis.com/experience/<itemId>?survey123=env:beta , which will use Survey123 beta envrionments for the Survey widget.

Please let us know if you still observe any issue in your workflow.

LoganLaudano

Same situation over here as well

ChessClaire

@ZhifangWang the HTML work around does not seem to be working for me and I am not sure about using the beta version because we have an Experience Builder (EB) with a Survey widget that are in Production. Any idea's, support or suggestions? Unfortunately, this is a work stopper for our programs using the EB Survey configuration.

AlexCarter2

I have a readonly text question that has no calculation used and it is causing this issue as well. Are we sure we need a calculation in that specific field?

ThomasHamill

Thank you @ZhifangWang, that workaround in your first bullet point with the suggestion to add HTML <p> tags around the read-only calculation appears to have worked and resolved the "Error: Initializing form... Error: not a object" pop-up with at least two other users also having tested and confirmed success.

ZhifangWang

Hello everyone,

We have identified an issue in the Survey123 May 2025 Update: when using Survey123 Connect, a calculation for a readonly text or note question may not function as expected and can even cause the survey to fail to load.

Current workaround:

For any note or readonly text question using a calculation, wrap the calculation in HTML <p> tags. For example, if the original calculation is ${int1}, change it to concat('<p>', ${int1}, '</p>'), then republish the survey.
Alternatively, for non-production surveys, use the beta version of the Survey123 website at https://survey123beta.arcgis.com, which includes a potential fix.

Note: ?version=latest in URL is the only supported value in the documentation. Unless you have fully tested, using an old version number may cause other issues.

We appreciate your understanding and have planned a fix for early next week to address this issue. Please let us know if you still observe any issues on the beta website.

ThomasHamill

This doesn't seem solved yet, as some users have reported being unable to make the "version=3.21" solution work.

Any way the team can disable/revert the Solved! Go to Solution indicator until a consistently reliable solution has been found?

ThomasHamill

Given this issue, for active surveys would it help to change the appearance visibility to hidden (on those calculations/note questions that might be causing the error)?

GISAdministrator_LMCC

Also getting this error in Experience Builder online, using the Survey123 widget to view previous survey submissions. When editing previous survey submissions, it works fine.

There's no option for me to change which version of the form is displayed, as there is no URL to edit.

GISAdministrator_LMCC

So for you survey try..
https://survey123.arcgis.com/share/dede88c993fb4d358cd0c7a534976c15?center=42.28321263,-87.84173499&version=3.21&field:appurtenance_type=Valve%20Vault&field:appurtenance_id=BV-001&field:appurtenance_globalid=158ba7e0-66dd-44f4-8741-deacf8677ed8&field:maintenance_leg=101#access_t

GISAdministrator_LMCC

i had success with placing it here https://survey123.arcgis.com/share/itemidnumber?version=3.21&field:....etc etc

JamesTedrick

Hello,

An issue has been identified with the display of the results of calculations in note questions or used in variable interpolation on the web form. We are working to develop a fix and deploy it as soon as practical. A possible workaround would be to use the ?version=3.21 URL parameter to revert to a previous version of the Survey123 web form.

KatyFlaherty

Hello Melanie,I republished my surveys using the 3.22 connect this morning, and had the same issue everyone else was having. The surveys are fine to be updated with 3.22 Connect but the Dashboard URL needs to contain 'version=3.21' and they will still work even with the version stating rematch.

Martin-E1

I'm having the same issue. Both options are for 3.22. None of our URL links to survey123 web app will load as of yesterday.

MelanieWhalen

Does anyone have an install of 3.21? I have 3.22 which doesn't work, and I cannot find a download file for 3.21.

Marc_Patti

Just tried inputting the "version=3.21" parameter into the survey URL and that did fix the issue (for now).

Seems likely that ESRI pushed some update that threw everything off in the last day.

gmontero

Thank you. It worked for me.

EddyClark

Getting the error too.

Marc_Patti

Started receiving this error in the web app today after I published changes from Connect. Nothing has resolved the issue thus far and we've lost access to a pretty critical inspection form for our township.

MelanieWhalen

This is not resolved for me. I have tried all of the above suggestions and am still getting an error.

SaadShahzad

Also running into this issue in Experience Builder survey widget.

Jaivik_P

It is the version issue. We had our survey set to Use latest version, so this error affected us with latest version of 3.22!

We changed the embedded URL to use previous version (version=3.21) and that fixed the issue temporarily.

joyoung_kerrvilletx

@bbywaterbw removing the ready-only from my calculation fields fixed the issue for me as well. My survey was published from Survey123 Connect at version 3.22. I did try using ArcGIS Online Assistant to change the version number in the Experience Builder JSON but that did not fix the issue no matter what version number I used.

SteveMartin__MDTA_

I'm almost positive it has to do with versioning and when ESRI makes changes.

bbywaterbw

Thank you for the suggestion. Unfortunately my options are the same either way and didn't have any effect when I used both of them.

I did get it to 'work' right now but am skeptical of what will happen on the next update. I am using url handling and passing information to populate survey fields. For some reason 1 field seemed to be causing the issue and out of desperation I changed it from a read-only (which all of the other fields are set to) to editable and that took care of it. I wouldn't call that a fix but it's working for now.

JasonJordan00

Can confirm its an issue with the latest 3.22. I just spent 2 hours trying to figure out how I broke my pulldata functions returning 'not an object' in Chrome dev tools only to realize thanks to above if I put version=3.21 they suddenly work.

SteveMartin__MDTA_

When I started out in Survey123, every time ESRI made a change it affected me adversely. It took a bit of figuring what was going on before I got the hang of it.

Just a hunch but open your form in the survey123 website and click settings. What happens if you set it to either one of these options?

SteveMartin__MDTA_

When I started out in Survey123, every time ESRI made a change it affected me adversely. It took a bit of figuring what was going on before I got the hang of it.

Just a hunch but open your form in the survey123 website and click settings. What happens if you set it to either one of these options?

joyoung_kerrvilletx

I am experiencing the same issue. I am not using the Embed widget. I am using the Survey widget. We have not changed anything in our environments for months. I am experiencing this with ArcGIS Enterprise 11.4.

bbywaterbw

I'm having the same issue, but my survey is not only in an embed, I'm also doing some url passing. Everything was working yesterday also. My Survey123 Connect is version 3.22.49. I wasn't using any version information prior to this issue and my url string would look something like this:

https://survey123.arcgis.com/share/(survey id number)?center=42.28321263,-87.84173499&field:appurtenance_type=Valve

Any suggestions where to slip the version information in? When I add it before the question mark or after the ampersand it makes it worse.

PaulSweeney3

@SteveMartin__MDTA_ yes thats it must be some browser update or something throwing it out i reverted back to 3.21 and it works for me now.

SteveMartin__MDTA_

I too am having the same issue. Today is the first time seeing this.

Rejoindre la conversation

Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.

Liens rapides

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