For some of our features, our symbology is based on a field that is calculated in Field Maps via an Arcade expression. The Arcade formula that determines the symbology type is based on the values of five other fields. When one of those five other fields is edited in Field Maps, in iOS only, we get a pop-up alerting "Changing Feature Type - You are changing the feature type. Would you like to keep your current values (where possible) or reset to defaults?" that then has the option to select Keep Current Values or Reset to Default Values.
We do not get this pop-up for features whose symbology is based on an editable field. We only get this pop-up for features whose symbology is based on a calculated field that is based on the values of other fields.
We do not want this behavior. But we definitely want to be able to use iOS products.
Is there a way to disable this behavior in Field Maps in iOS?
We are using Enterprise 11.1. We plan to upgrade to 11.3 in a few weeks. Maybe this is a bug that is resolved in 11.3???
This may not necessarily be the solution but more of an idea suggestion. The popup language sounds something to what I get when editing fields that have subtypes in Pro. By chance, do one or more of your fields use subtypes?
Thanks for asking, @Eugene_Adkins . That was a good clarifying question!
We do not use subtypes, related tables, attachments, or attribute rules. The layers are referenced from our archive-enabled, non-versioned Enterprise postgres database. They are simple points, lines, and polygons with quite a few domains, simple templates, and a few default values. The only thing that is "fancy" is that I have lots of Arcade expressions set up for use in Field Maps to optimize efficiency and reduce data collection errors in the field.