I have a feature layer coming from a Survey123 database. I want to display data only for the current day from todays surveyors in the field on a webmap so that I can produce a dashboard of which sites fieldworkers have visited today and where they have last visited. I thought this would be simple! but the Filter Condition "in the last" seems to have a bug - it doesnt include todays data points ( at least for several hours after submission). For example I can add a data point for today 3rd November 2024 - this will not be included in filter results set up on either Survey123 or webmaps for datapoints with a date "in the last" 2 days. However it is included in filter results set up for datapoints with a date after 1st November 2024. I cant find this as a known bug but it is happening on all the data sets I have tested it on. I need the data on my dashboard to be current and reliable for safety reasons but I dont want to have to go into the webmap every day and refresh an "is after " filter with todays date.
Can anyone help me or have a workaround? Many thanks
I have found a partial work around for this issue. I have set up the survey123 form to automatically record "Date" using the Date selector in Survey123 Connect and the "in the last" bug/error occurs on this field. However Survey123 also automatically records an EditDate field which is date:time the "in the last" filter condition works on this field.
Is this a DateOnly or classic Date field? If it is a Date Field survey might be capturing a time like midnight and then the database stores it in UTC which could be placing it on the 1st instead of the 2nd.
The field is date only as supplied by the drop down option for "date" in Survey123 Connect . Only the date is displayed in Survey123 or webmap. If time is being capture with that date it is not obvious. if Filtering using the "in the last" on a date only field doesnt include recent data recorded for the current day then is this being looked at as an issue by ESRI?
I would need to see the layer and I can take a look.
I do not have a open issue on the internal dev side for this and I do not have a support ticket for this.