We are now implementing form calculations in Field Maps on several projects and these have been a big help... some bugs to work through, but overall pretty good so far.
By design, a form calculation renders the field un-editable from within the form. This leaves me wanting a little bit as I have use cases for a calculation that fires once and only once on insert/creation but allows the field to remain editable. Call this calculated default values. Separate from a database default value of the underlying feature service and those set in feature templates which are both examples of static default values.
The classic use case is a date field (not a system date field like editor tracking)...
On insert set the date to today. e.g. return Today(); or return Now();. However, allow the field to remain editable so that a user can make a change. 90% of the time the user would need Today's date and when this event fires the user can ignore the field, but in the event that they are recording an inspection/event that occurred yesterday, today, then allow the user to manipulate the date.
By design it could be a different category of a form's field capabilities.
Currently we have
Can an option be added for these types of cases? Calculated Default Value Expressions?
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.