Smart Forms: Editable and Required Logic

Question

I have the following logic written on a date field called Trapping Start Date:

Editable: Trapping Start Date is editable if Baiting Start date is not blank

Required: Trapping Start Date is required if Site Status = Trapping

Essentially, I am trying to prevent staff from entering a trapping start date if they have not entered prior information about baiting. Therefore, they should not be able to submit trapping data if baiting data has not been entered. Given the logic above, it should work.

When I try to submit a Trapping record with no prior data, the Trapping Start Date is not editable (good!) but if I try to click submit, the record will submit anyways, even though Trapping Start Date is a required field.

Has anyone else had this issue or know of any work arounds? I am having this issue on 3 different fields where I have editable logic dependent on another field being 'is not empty'.

NathanDavis · Answer

@DanielFox1 wrote:ArcGIS Field Maps enforces required fields only if they are editable at the time of submission.

Is there documentation on this? We're using Field Maps v 25.2.0 and this is not my experience.

NathanDavis · Answer

If TrappingStartDate is not editable, you're controlling that with an expression or a checkbox in Field Maps Designer.  Sounds like that needs sorted out.

As for the preventing data entry, I would do it with visibility.

vis_trappingStartDate = if (IsEmpty($feature.Baiting Start date)) { return false }; return true;

The required expression would be identical, right? if Baiting Start Date is empty, return false.  Else return true.

I would leave the field editable all the time.

CASSIEANGERER · Answer

Thanks so much for this information.

When I tried the line of Arcade you provided in the calculated expressions in Smart Forms, on the mobile interface it did block the form from being submitted if entered incorrectly (good!). However, when the order of data was submitted correctly (when baiting start date was entered first), then Trapping Start Date was not able to be edited. I assume this is because if a calculated expression is placed on a field then it is not edited? Any ideas on a work around on this?