Required field and calculated expression not working as intended?

[TeamGEOHHSK]

Hi all,

A form made with Field Maps designer includes an attribute "CODE" that is automatically calculated based on the nearest surrounding object. See example 7 from this blog. The field is set to required. When there is no surrounding object the field is empty and an Info box appears that states that the user has to place the point closer to an existing object.

In the mobile field maps app (iOS) this works fine: the attribute is calculated if an object is near and when it is not the info box appears and the form cannot be submitted.

When I do the same in a Web Map or with the Edit widget in ArcGIS Experience the attribute does calculate correctly, but when there is no surrounding object the Info box doesn't appear and more importantly I can still submit the form.

Is this a known limitation/ bug or am I doing something wrong? 

[JenniferRead1]

I am having the same issue trying to do example 5 from that blog. When I hit update on the web map it just freezes when I hit create.  It works just like it should when updating via field map app.  

[JaronJensen7]

I am having the same issue. I am running a check to make sure certain values add up correctly for fiber and conduit footages. If they don't add up I have an error check that runs that won't let them submit the bad data. It works in field maps, but not in the edit box of experience builder. It lets them still submit the wrong footages. The error check is its own calculated footage so I don't want them to edit it.

[VanessaSimps]

has anyone gotten any feedback/solutions for this? we noticed this, it seems you can’t auto-populate an editable field, and since fields that use calculated expressions need to have editing disabled, we can’t make it a required field. 

The issue is that staff can save and leave the field empty. Not ideal!