idea Experience Builder- Edit Widget- Ability to create required fields in ArcGIS Experience Builder Ideas

Experience Builder- Edit Widget- Ability to create required fields

Amanda__Huber — Mon, 08 Aug 2022 18:46:25 GMT

Hello Experience Builder Team,

Please create a way to manage field requirements through the Edit Widget. Currently there is no way to make fields required/not required. This will allow admins to ensure data quality.

EB Edit Widget Field Configuration- There is no way to make certain fields required:

Thank you,

Amanda Huber

Re: Experience Builder- Edit Widget- Ability to create required fields

MavTucker_CoMo — Fri, 06 Jan 2023 20:36:18 GMT

Please! The "created" feature currently disappears (doesn't create) without warning if not all fields are filled out, and instructing users to add placeholder data messes with SQL queries and views already created and in use elsewhere.

Additionally, date fields require a time even when it is turned off in the pop-up.

Re: Experience Builder- Edit Widget- Ability to create required fields

PeterKT — Tue, 28 Feb 2023 04:10:31 GMT

We have 10.8.1 Enterprise and are still using the old web map. No matter what I do in the fields configuration it makes no difference. I just suspect the old web map is the cause. Hoping 10.9.1 upgrade will fix this.

Compulsory fields and maybe some of the Field Maps functionality with semi-smart forms would be good.

Why would I want to edit ObjectID?!?! 🤔 👇

Re: Experience Builder- Edit Widget- Ability to create required fields

Jennifer_Parmeley — Wed, 05 Jun 2024 12:44:13 GMT

Has there been any movement or feedback on this one?

I use Boolean fields in our data sets to display map points.
Is this facility active? (yes/no) This allows users to remove a point from a map and prevents accidental deletion.

This appears to be available if you use a form.

Re: Experience Builder- Edit Widget- Ability to create required fields

Marc_Patti — Fri, 20 Dec 2024 21:32:11 GMT

Also interested to see if there has been any movement on this. I'm glad that we can still make certain fields required using the smart forms in Field Maps, but this really seems like a feature that should be configurable in Experience Builder itself.