You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Making an Address field "required" is slightly complex. There are up to six normal subfields, plus the coordinates & zoom fields.
So... which subfields must be completed in order to fulfill the requirement?
We can assume the Latitude and Longitude subfields (but not Zoom) should be considered "required". This makes sense, but may not truly account for all scenarios. So ideally, we would like to make the required subfields configurable.
If all goes according to plan, you will be able to decide which subfields are truly "required". By default, only the Latitude and Longitude will be required.
This feature is expected to be released as early as v4.1, or as late as v4.3. If anything changes, I'll post back to this thread!
If all goes according to plan, you will be able to decide which subfields are truly "required". By default, only the Latitude and Longitude will be required.
Just to clarify – will it be possible to make latitude & longitude not required? This is important for our use-case. We're using an address field to enter an address and/or a geolocation. But not all entries have a geolocation, so some leave the coordinates empty (for example, some entries just have a PO box as their address, so no geolocation that makes sense to display on the map).
Maybe this is already part of the plan, just wanted to point it out in case it isn't :)
Making an Address field "required" is slightly complex. There are up to six normal subfields, plus the coordinates & zoom fields.
So... which subfields must be completed in order to fulfill the requirement?
We can assume the Latitude and Longitude subfields (but not Zoom) should be considered "required". This makes sense, but may not truly account for all scenarios. So ideally, we would like to make the required subfields configurable.
If all goes according to plan, you will be able to decide which subfields are truly "required". By default, only the Latitude and Longitude will be required.
This feature is expected to be released as early as v4.1, or as late as v4.3. If anything changes, I'll post back to this thread!
The text was updated successfully, but these errors were encountered: