Survey123 Connect currently allows users to run the “Analyze” tool to check for issues before publishing a survey. However, it does not flag the use of reserved keywords in field names—despite these causing critical publishing failures when deploying to ArcGIS Enterprise (e.g., generic “Error 500” messages). This results in wasted hours troubleshooting something that could be caught earlier.
Yes, Excel will throw an error if you manually type a reserved word, but many workflows involve copy/pasting from previous surveys—bypassing that safeguard. And while AGOL may allow publishing, ArcGIS Enterprise does not, making this inconsistency even more frustrating.
This isn’t a bug per se—there are mechanisms in place—but it’s a missed opportunity for the Analyze tool to proactively help users avoid a known pitfall. A simple enhancement to check field names against the reserved keyword list would save time and reduce user frustration.
