Smart Forms work in Field Maps but not Map Viewer - Continually loads

[CASSIEANGERER]

I am working on a form to use in Field Maps. I built the form in Field Maps designer. There's approximately 40 fields. I am using conditional visibility, calculated expressions, and other logic statements on every field. The form works seamlessly on Field Maps, but when testing the form in Map Viewer and Experience Builder, the edit widget continually loads.

I have a different layer in the same map with a form configured in Field Maps designer with approximately 10 fields and it works great in both Field Maps and Map Viewer. 

Does anyone know what could be causing this to happen?

[bbollin]

hi @CASSIEANGERER, I'd need to take a look at the form and any expressions to see what is going on. Are you able to share the webmap/layer with me? If not, please reach out to support and get an issue logged so the team can investigate 🙂

[CASSIEANGERER]

I found the error. I had logic on field written so that "Site Status could be edited if Take Date is Null". When I removed that logic, it worked fine. However, with being able to test in a Web Map now, I have found another issue: 

I have a required calculated field set up for Validation that checks to make sure dates entered are in the correct order. If dates are submitted in the wrong order, the calculation returns Null. In Field Maps, it works flawlessly and will not let the form submit. In a Web Map or Edit Widget within Experience, the form will still submit even though the field is set to Required. I found another blog post where multiple users are having the same issue and have not found a solution. Do you have advice on this? This is a huge limitation for data collection. 

[EmilyGeo]

Hi @CASSIEANGERER, 

Is the calculated field a text field? If so this could be related to a known issue in Map Viewer. Often the template for a text field contains a space, so even though you can't see any text displayed in the field, the Editor reads the field as not Null.

As a workaround, you could try updating the template,

or using a different field type.