topic Re: Datefields cannot be forced to be null in ArcGIS Survey123 Questions

Datefields cannot be forced to be null

RasmusHolstMikkelsen — Mon, 08 Mar 2021 09:45:12 GMT

Hi.

I have made a Survey in S123 connect based on a current feature service, where the user should be able to change 3 different date fields (among other fields).

To make it more user friendly, i have made 4 buttons in an experience environment, where the date fields would be either today's date or null, as the 3 fields are connected (Reservation date, when the reservation will expire, and the date when the property is sold)

When there is a new reservation, the user will click the "Reservation" button, and the "Sold date" will become null, "Reservation" will be today's date, and "Reservation expires" will be today's date + 6 months.

My issue:

When the button is clicked, the following is hard coded into the Survey 123 link:

https://survey123link?mode=edit&globalId={globalID}&field:Status=Reserved&field:Solddate=null&field:Reservation={Today}&field:ReservationExpires={Today_6Month}&hide=field{someFields}

This hardcoded link results in the following survey, where the "Solddate" would become null (Which works as intended): - Translated from Danish (Sorry)

However, when you click the submit button i get the following error:

Which i would roughly translate into: "The survey contain errors: 1. Click here to navigate to each error".

So for some reason it is not possible to send Null data to a datefield? Does anybody know why? - The field(s) can contain Null values in the database. The 3 date fields all have the bind::esri:fieldType of esriFieldTypeDate in the S123 excel spreadsheet.

Re: Datefields cannot be forced to be null

IsmaelChivite — Tue, 09 Mar 2021 04:26:07 GMT

Did you try removing &field:Solddate=null completely from your link?

If you do not set a default value in your date question, it will appear empty and if not completed by the user a null value will be stored in the feature layer.

Re: Datefields cannot be forced to be null

RasmusHolstMikkelsen — Tue, 09 Mar 2021 07:01:01 GMT

That works completely fine, however, as the feature service is editable, the "&field:Solddate=null" was my way of trying to reduce the amount of clicks when editing the data. Therefore, if i don't set "solddate=null", the original date will still appear, if already set, and it would then have to be changed manually 🙂

I want to be able to remove the original date stored in one of the date fields, without the user needing to delete/remove the data manually.

Re: Datefields cannot be forced to be null

JerrySneary — Fri, 29 Sep 2023 21:28:18 GMT

Hi @RasmusHolstMikkelsen & @IsmaelChivite ,

Have you figured out how to do this? I'm currently in a similar situation. I have a form with a status field and date fields for each status. One of my statuses is "Needs Repair". When "Needs Repairs" is selected the date and time is recorded. When the status is changed back to "Live" I want the date that was recorded to be removed (blank). I can have my field crew manually remove the date in the form, it's just one more thing that they can forget to do manually. I'd rather have it automatically done with the status change. Also, this is in a web form not the field app.

Re: Datefields cannot be forced to be null

vaishalikulkarni00 — Thu, 04 Dec 2025 21:29:40 GMT

2025 and I'm still trying to figure this out. I have the opposite problem. The date in my feature service is null and I want the survey to pre-populate with the current date "now()". For what I can gather, no matter what you do, if you use mode=edit in the link, it'll bring over the attribute that's in that cell. No amount of arcade expressions, adding &field:Solddate=null in the link or adding defaults or calculations in the survey will change that.