topic Re: Survey123 Overview Tab Not Loading in ArcGIS Survey123 Questions

Survey123 Overview Tab Not Loading

ak_gis — Mon, 11 Jan 2021 21:45:04 GMT

We have a survey published to client's ArcGIS Enterprise 10.51 and its overview tab https://survey123.arcgis.com/surveys/[itemID]/overview is failing to load. When I check the query requests, it looks like it's querying the creation date field in daily interval until it reaches the current time. In our test environment, where the same overview tab works fine, this is the last query request (today is Jan 11th, 2021)

With the problematic overview tab, I see the last few query requests' where statement is querying tomorrow's date. Can this be the culprit of why the overview tab is failing to load and freezes the browser? I asked the client to check the time zone of the editor tracking fields as well as the server machine's clock.

Another difference between our ArcGIS Enterprise set up is the database type. My test environment is set up with SQL DB, whereas the client uses Oracle DB. If you know what I should look into next or how to fix this, please let me know. Thank you for reading! 🙂

Re: Survey123 Overview Tab Not Loading

ak_gis — Tue, 12 Jan 2021 19:34:12 GMT

More findings on this:

It turns out the client's feature service doesn't like the where statement that the overview tab is using:

What Survey123.com overview tab is asking: CREATIONDATE >= '2020-03-12 20:45:03' AND CREATIONDATE < '2020-04-12 20:45:03'.

What the feature service accepts: CREATIONDATE >= timestamp '2020-03-12 20:45:03' AND CREATIONDATE < timestamp '2020-04-12 20:45:03'

Interestingly, my test feature service understands both of the where statements and returns result. Only difference between the two environments is the underlying database (SQL vs. Oracle).

Re: Survey123 Overview Tab Not Loading

MaddieMooreDEQ — Wed, 20 Sep 2023 15:40:27 GMT

I am currently experiencing this same issue with Oracle and the timestamps query not allowing the overview page to be used. Was there any solution/work around to this issue you ran into @ak_gis ?