topic Re: Field Maps - Required Fields Not Working as Expected in ArcGIS Field Maps Questions

Field Maps - Required Fields Not Working as Expected

Tolo__AdamTolo — Wed, 24 Feb 2021 03:56:45 GMT

Hey all,

I have been using ArcGIS Field Maps mobile and have noticed that the fields I have setup as "Allow Null" = False, don't need to be filled out when i tap "Submit".

I setup the form for the layer using ArcGIS Field Maps web app and the fields have the "Required" marked as True.

In the Field Maps mobile app, I have the asterisk next to the field indicating that the field is a required field.

In Beta, I noticed that it was released in October:

Is anybody else experiencing this?

Re: Field Maps - Required Fields Not Working as Expected

CharliePhilbrick1 — Fri, 19 Mar 2021 21:31:22 GMT

I too am experiencing this. I published the service I'm using from ArcGIS Pro and while the expected fields shows up in field maps with the '*' indicating that it is required I can Submit features without even touching those fields.

Perhaps related issue: I have two fields that have no default value set that are populating in field maps as '0' (zero). Strange behavior. Worse, this is behavior that undermines what I consider to be essential functionality of the app and underlying stack - this is a key way that we maintain data quality in our field collection efforts.

If anyone has some insight for @Tolo__AdamTolo and me, please pass it on!

Re: Field Maps - Required Fields Not Working as Expected

Anonymous User — Sat, 20 Mar 2021 00:11:11 GMT

Can you check your feature layer templates (specifically the layer definition json)? It's possible that the default values for those fields are set to empty strings or 0 instead of null. Since there technically is a value applied by default, the submit button will allow you submit the feature.

You will not be able to see this difference in Field Maps web - you have to look at the layer definition (json). There is also a script for Collector (but it applies here too) that can change those value to null. Field Maps web does not inspect the default values of the template, it only checks the nullability of the field.

Re: Field Maps - Required Fields Not Working as Expected

CharliePhilbrick1 — Sat, 20 Mar 2021 03:46:10 GMT

Thanks for your quick reply, Aaron.
Digging in to the json sounds like good actionable advice, however when I attempt to access the REST endpoint for the service, I get a 'Token Required' error.
Would it be helpful to share this AGO item with you? I don't know what all you need to know about my account and how this service was created, but here's a little: I created it in Pro and shared as a web layer to my organizational account where I have a Creator account type. I'm happy to provide more details if they could help me past this Token-related roadblock.

Thanks again,
Charlie

Re: Field Maps - Required Fields Not Working as Expected

Tolo__AdamTolo — Mon, 22 Mar 2021 00:01:22 GMT

So the default value is null:

Interestingly, when I click on the field, I have noticed that little number '1' in the right hand side. If I back space, I then am not able to submit the sighting before completion.

Looks like there is an empty space.

Also my fields that have domains and are not free text behave the same. I can submit a feature without filling out the required field but if I select one of the domain values and then go back to selecting no value, then I can't submit the feature.

Looks like a bug to me?

Re: Field Maps - Required Fields Not Working as Expected

Anonymous User — Mon, 22 Mar 2021 14:08:13 GMT

@Tolo__AdamToloThe first screenshot you sent is looking at the field default value. Collector and Field Maps uses the default value store in the "templates" property, not the fields default value. The behavior you are seeing does align with my hypothesis regarding your templates.

This is where you need to check (you may have multiple templates within the "types" array):

@CharliePhilbrick1Yes if you and/or @Tolo__AdamTolo want to share your layers with me you can add the map and layers to a group and then invite the "arcgisfieldmaps" username to that group.

Re: Field Maps - Required Fields Not Working as Expected

CharliePhilbrick1 — Mon, 22 Mar 2021 18:57:56 GMT

Thanks again, @Anonymous User for engaging on this stuff.
I've just invited 'arcgisfieldmaps' to join a group called 'ESRIFieldMapTesting'. Let me know how you'd like to proceed from here.

Re: Field Maps - Required Fields Not Working as Expected

Tolo__AdamTolo — Mon, 22 Mar 2021 22:45:53 GMT

@Anonymous User you are right.

So my question is where did this get set? I definitely did not set it up like this.

I will have a bit of a play around and report back.

Re: Field Maps - Required Fields Not Working as Expected

Anonymous User — Mon, 22 Mar 2021 22:58:35 GMT

Templates can be defined in ArcMap or Pro and then will be published as part of the feature service. You can manage templates in two places in ArcGIS Online:

1. In Field Maps web

2. In Map Viewer (Classic)

In Field Maps web if you open the map and select the layer, then select the Templates tab you can configure the default values for each attribute for each template. If you click on an attribute, you can backspace to remove the empty values and then when you Save the layer it will write null to the feature layer template default value(s), which is what you want in this case. The same thing applies for numeric fields.

If you have many layers that you want to fix, you can use this script/toolbox.

@CharliePhilbrick1I checked your layer and you have the same problem.

Re: Field Maps - Required Fields Not Working as Expected

Tolo__AdamTolo — Mon, 22 Mar 2021 23:48:47 GMT

Ohhhh. Thanks that clears things up a lot @Anonymous User

So by default, after publishing, I need to go through and adjust this template? FieldMaps web seems to have put in spaces for free text fields and for the fields with domain lists, I have to select the value "Not selected" so that message "must match one of the options" does not show up.

Would think it would default to these from the start?

Re: Field Maps - Required Fields Not Working as Expected

CharliePhilbrick1 — Fri, 26 Mar 2021 20:17:24 GMT

I finally got the chance to try this out today and it worked like a charm. Thanks for all your help, @Anonymous User . Pointing me to the ability to edit those templates in Field Maps Web was particularly good as I had still not taken the time to check out that interface and I think it will serve me well moving forward.
I did experience some of the same frustration and/or confusion that @Tolo__AdamTolo mentioned there, namely that for non-nullable fields with a domain and without a default value I had to change each one to 'Not Selected' before I was able to save my changes to the template. This is not a big problem, but I agree with Adam that it's not the behavior I expected.
Onward!

Re: Field Maps - Required Fields Not Working as Expected

DougBrowning — Tue, 28 Jun 2022 18:09:07 GMT

I think this one is getting me today. Maps we had for a few years now no longer forcing the required fields all of a sudden. I am using all Map Viewer Classic. I have not touched anything in Field Maps web. Just a straight publish from a GDB in ArcMap.

I tried the process posted to update the template but it did not make a change.

I see the space in templates.

But when I go to fix it in templates it has no space.

I have tried adding and then removing a space and a few other things but it still stays with the space in the JSON.

Nullable is set correctly

LOCAL_ID (type: esriFieldTypeString, alias: LOCAL_ID, SQL Type: sqlTypeOther, length: 255, nullable: false, editable: true)

I then tried the linked script but we have 2 factor so it fails. Not sure why it would ask for a un/pass when it can just use the Pro login.

Unable to generate token.
Invalid username or password.
(Error Code: 400)

So now I am stuck. Only some of my services are doing this. Maybe a diff between publishing with Pro or ArcMap. Is this some new bug? If so is it getting fixed?

thanks