Is it possible to set the date to automatically enter the current date in Field Maps form? I have tried using these expressions, now() and today() but you still have to click into the field and select the date from a calendar that appears.
This worked for me when I first created my Field Map last year. I am making some changes to prepare the app for next season, and found that this is no longer an option. I have to choose to either calculate the date OR let the user input it manually. If both things are enabled, then the user has to input the date manually, there is no calculation. Frustrating
this has worked for me, thanks!
When I manually typed in now() I had problems. When I went to the (fx) expression search and clicked on the option for now() it worked.
I field maps designer you can add the calculated date to the field. In the form, select the field to open the properties. All the way at the bottom is the option to calculate a value.
I was also looking for an answer to this. I know this is possible through survey 123. It would be great if it was also for field maps forms. Survey123 has more capabilities.
I'm using Field Maps in the new map viewer, and I have to enter in the date as text (no calendar box opens). I tried the trick above (allow nulls, leave blank, required) but the result is still empty. Any tips? @CBeck17
Curiously when I set a different field (Name) to equal the Creator, a new feature saves without any value. But when I Edit the same feature, suddenly the Name is populated properly.
Oh I have to use Classic map still since no related tables yet. Also they have tables in a diff spot then feature layers which is just plain weird.
Thanks!
Allow nulls was configured in the fields configuration in Pro. Required was selected in the form editor for field maps. Not ideal but it works well.
I thought not allow nulls was how you set read only. Did this change? Where did you set this?
Thanks
My solution was to allow the table to accept null values but for the date field to be a required field. It defaults to the current date and time that way.
For those of you who haven't done so already, I'd encourage you to comment/contribute to this idea.
It is happening so often I added some Arcade to the popup to help point it out to crews.
Set the formula (for us anything not this year is bad)
Check FieldEvalDate {expression/expr33}if (Year($feature.FieldEvalDate) < Year(Today())) { return "Warning you have entered a bad date!"}else { return ""}
Then in the popup text add the expression in red.
Crew sees
Hope that helps
Could this be added as to the ideas page? Really frustrating especially the 1899 date - not sure why ESRI think this is acceptable.
Anyone else have any workaround here? It is already creating a QA nightmare for us. The point of required was to solve issues like this. But instead of it starting blank and forcing the user to pick it defaults to 1899 so the user just skips it and keeps going.
I do not see a way to default to today? The field default wants a static value not a formula. Note I am on Map classic.
Any ideas? thanks
We noticed this today as well and we could not get it auto-opulate. I think it would be very useful as it will keep the number of clicks that field users need to make to get their job done.
I also have found that if you make a Date field required (set not allow nulls) then the date defaults to 12/21/1899 for some reason. The user must manually hit the today button, which most forget to.
Where is the 1899 coming from? If you are going to prepopulate a date it should be today.
thanks
Signed in members can post, follow updates, and more. New here? Register a free account.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
