Default Values not working in Field Maps Mobile

I spoke with Esri and was informed of the following bug: BUG-000144318 - When you publish a layer from ArcGIS Pro to ArcGIS Online that has default values set on at least one field and there are existing features the default values will not show up in ArcGIS Field Maps web app Smart Form Templates.

They informed me of the following workaround:
You can export a FGDB in ArcGIS Online from the hosted feature layer that has these default values setup and then publish a new hosted feature layer copy from this FGDB. This copy will not exhibit the behavior. Note that this will be a distinct layer and will not have a service definition. Meaning that you can't overwrite it from ArcGIS Pro like the original layer.

DougGreen

Kristin, I'm not sure what's going on with yours and I just realized yours is a hosted feature layer. We have a non-hosted enterprise feature layer. But here's what just fixed it for us.

Remove the defaults on the layer and save
Add the defaults back and save

For us, we had to republish, but with yours being hosted, I'm not sure you can republish. But you could simply try removing the defaults and re-adding them.

All comments

AlexVideka

Amazing find Dan! This is the much more feasible workaround while the bug still exists. Worked perfectly for me!

DanMakridakis

For anyone still dealing with this issue. I've found the cause and workaround when publishing from Pro to ArcGIS Server.

If the feature template inherits the default values from the feature class schema, even though it appears in the Pro feature template, it will not be pushed into the published service and therefore will not work in Field Maps. As others have mentioned, for it to publish with the service, you need to trick it into thinking the default is uniquely set for that feature template. However, you don't need to do as many steps as others have suggested (change, save, change back, save, republish). You can simply change each default in the feature template properties to anything else, and then change it back to the default before closing the properties. You can do this to all of your feature templates before saving the project and re-publishing the service.

One trick to determine if a default value is going to publish, is to look for a Grey bar next to that field name while in the feature template properties. If there is a Grey bar next to the field, then it's recognized as a unique default and will publish. When tricking it, you want it to appear with a Green bar next to the field, meaning it thinks it has changed. After accepting the properties the Green bar will change to Grey. If the bar next to the field is Blue, then it will not publish. If you to click on a default drop down and select the same value, you will see the field remains Blue because it knows it is the same value and nothing changed. This is why you must first change it to something else and then back to trick it (no need to close in between).

In the example below, 'Enabled' and 'AncRole' have Green bars next to them indicating they have been altered since opening the properties (inherited default was changed to something else and then back to the default). After closing and reopening the properties, they will have a Grey bar next to them, as is seen next to 'Segment' and 'GIS Status' which were previously changed. 'Owner' has a Blue bar next to it even though it has a default value, as do all the field without default values. In the current state, 'Owner' would not have the default published with the service, but the other 4 fields will.

AbiDhakal

Hello@DougGreen

In ArcGIS Field Maps, when I try to change the default value it is greyed out. It shows the default value I set in ArcGIS Pro that I'm using in another Field Maps project, but I want a new default value for this new project and I cannot change it to a new default value. It is greyed out in the template too. I will appreciate your input.

Thank you,
Abi

AaronCole1

That's great, happy to provide some direction, even if not the solution. I stumbled with this for a little while.

I was able to set a default value for a hosted feature service in Pro just now. I wonder if that is a recently added capability?

Attribute default values are a property of a specific feature template. You could create multiple templates with different default values for different situations. You can also select the default tool for editing, among other things I'm sure.

https://community.esri.com/t5/arcgis-field-maps-questions/default-values-not-shown-and-not-configurable/m-p/1256698/highlight/true#M5312

@AaronCole1, thanks your help!

You pointed me in the right direction. I'm using a hosted feature service however, so I could not do the changes you mentioned in Pro. I continued searching, found this thread and then managed to add a template through the API.

I'll post my code in that thread for anybody looking for a similar solution.

However now I wonder what is the use of the default value in the layer definition? What is the difference between the template and the default value ? 🤔

Thanks!

AaronCole1

This is what worked for me:

My problem is for a table. I don't think I can set feature templates for tables?

I'll see what I can do with arcade.

Thanks!

fklotz

Another workaround: Set your default value using the feature templates

Not a workaround, but if you don't need a 'default' and instead need to set the value in a field, you can use Arcade to do that in the Field Maps form.

Default fields still not working in field maps.

Tried deleting field and readding it. Still doesn't work for me.

AaronCole1

You'd think we'd have advanced beyond that workaround in 2022...alas...job security.

MarkPalmer

We are in the same situation - publishing from Pro from an Enterprise gdb and trying to access defaults via Field Maps. Sounds like we are SOL until this bug gets fixed? Do you know if it still worth filing a ticket with ESRI? Our offline maps are also failing to work with Enterprise layers, but that's a problem for another thread. 😉

fklotz

I've run into the same issue and ESRI told me that the BUG is still active. 1 of 6 layers in a Hosted Feature Layer, which were all set up similarly when the schema and map were designed in ArcGIS Pro, had default values on two fields which were not recognized by ArcGIS Field Maps. ArcGIS Online would not let me remove the default value from the field. ESRI attempted several solutions, none of which worked and they are still working on my case. ESRI's solutions were somewhat long and involved and included things like exporting to a gdb on ArcGIS online and then publishing a new layer from that gdb.

While ESRI is off doing some testing...

I figured out my own solution. The solution for me was to delete the fields in ArcGIS Online and then add them back in (also in ArcGIS online) in exactly the same way (with the same default values, same domain entries, same field type, same length, same name and same alias). If I had needed to keep the data in the fields, I would have added and calculated temporary fields to hold the current values before deleting the offending fields, then after adding the new fields, calculate them from the temporary fields, then delete the temporary fields. When I opened my maps, in which I had previously customized the layers and forms, everything was working as expected - the fields which had been replaced showed up as they should without even having to re-add them to the forms.

You could also contact Technical Support and have your case associated with that bug number or this one BUG-000146187; both point to the same issue.

AnneSanta_Maria1

I did notice that. We are publishing from Pro from an enterprise database so the workaround isn't feasible for long term data management. I'll pay attention to this thread and upcoming events so I can follow any progress made.

@AnneSantaMaria did you publish the layer from Pro? There's a known issue with publishing layers from Pro that was referenced earlier in the thread. If you're not publishing the layer from Pro, can you clarify how it's published?

thanks, Craig

AnneSanta_Maria1

We are currently experiencing the same issue with default values not sticking in field maps, even though the JSON indicates it is set and feature templates have them AND the database has the information set. We are using Enterprise as well.

@CraigGillgrass I am tagging you as a starting point for helping us get direction on this issue.

JessicaWay1

We are having the same issue with the defaults not showing in the Field Map App. However, they default values are showing when acces through the Web Map. We have tried to turn off/on the default values but that is not working. The defaults are showing in ArcPro but not in the app. The issue in the app appears on both iOS and Android devices.

Please see the attachments. All fields should have a default answer as No.

App_defaultsmissing.jpg

Capture2.PNG

DustinHall1

Hi Sophie, did you ever get this resolved? Having a similar issue with Field Maps / Collector. In ArcGIS Pro, the feature templates show the default value, when published the REST shows the default value, the default values work when I work on Portal webmap but when I go make a edit within the App, default values don't get added. Never had this issue before....

Are you able to invite the "craig_sp" user to the group so we can take a look at the layer and web map?

It is now showing in templates (I've re-uploaded the layer a few times by now) but still no default value when adding a point in Field Maps 😕

ok, are you able to set the Default Value for the field under Templates and does that then allow the Default Value to show up in Field Maps mobile?

No default values show in the templates tab on field maps... but it shows in the data area of the web feature layer.

@SophieWatts have you tried setting the Default Value for the field on the Templates tab?