- 500: Error performing apply edits operation

765
3
Jump to solution
03-13-2023 04:51 PM
fyang
by
New Contributor III

Hi there,

When I summited the s123 form on browser, it gave me the error like:

Failed to submit. 

- 500: Error performing apply edits operation

Any clue? Thanks!

Fan

0 Kudos
1 Solution

Accepted Solutions
fyang
by
New Contributor III

I just recreated the s123 form and published as new one with existing feature service. And the problem is gone. Looks like each time rebuild the feature service I need to recreate the s123 form again. Thanks!

View solution in original post

0 Kudos
3 Replies
ChristopherCounsell
MVP Regular Contributor

A 500 error is a generic server error. There can be a number of reasons why you are seeing this. Can you provide more information?

  • Survey published through Survey123 Connect or the web designer?
  • If Survey123 Connect, can you share the XLSForm?
  • Have you successfully submitted surveys this way in the past?
  • Are other users impacted? 
  • Are other surveys impacted?
  • Have you made any recent changes?
  • Are you working in ArcGIS Online or Portal for ArcGIS (ArcGIS Enterprise)?

More information will help narrow it down instead of wildly speculating... but if I had to I'd guess that there's something in the form design that's making an error submitting an edit. Like an invalid value, or something that's supported only in the field app but you're trying to use the web form where it's not supported.

0 Kudos
fyang
by
New Contributor III

Thanks Magisaian! Here are the information related. Hope it helps. 

  • Survey published through Survey123 Connect. It works well on connect.
  • Yes, I've successfully submitted surveys this way in the past.
  • All other users impacted. 
  • no other surveys related in the same portal.
  • This survey is based on existing feature service. The feature service been republished recently. And I republished the survey with new feature service url.
  • ArcGIS Portal
0 Kudos
fyang
by
New Contributor III

I just recreated the s123 form and published as new one with existing feature service. And the problem is gone. Looks like each time rebuild the feature service I need to recreate the s123 form again. Thanks!

0 Kudos