Select to view content in your preferred language

Contingent values - general question

314
2
Jump to solution
07-01-2025 07:10 AM
JayHodny
Frequent Contributor

Hello.  I am working on a project that inventories trees with name, genus, species, and family fields.  We are not using the Esri tree management solution for now, but I did snitch the species roster.csv file from the solution for our use.  My desire is to enter the common tree name, for example, Alaska-Cedar, and have the remaining fields autopopulated with the correct genus, species, and family values pertaining to the tree selected - at least that's how I think this should work.

I have created coded value domains for each field, assigned them to their respective field, created contingent_values and field_groups.csv files, and ran the Import Contingent Values GP tool successfully.  I jump into the attribute table directly and click in common name and select the common name for the tree I want to add to the inventory.  I was expecting to see the remaining fields populate with the corresponding values automatically.  I end up clicking on each field, searching each list for the correct values (using the original roster.csv as reference), and selecting the values.  When I get to Family there is one correct choice visible.  If I stop anywhere along the way, this error pops-up.  I also see the same error when I try to the Create Features tool and select the feature class.

JayHodny_0-1751377931391.png

I cannot figure out what is amiss.  Our arborist noted species populates based on common name, genus based on species, and family based on genus.

Field_Groups.csv

JayHodny_1-1751378603462.png

Contingent_Values.csv - value1 is common name, value2 is species, value3 is genus, value4 is family.

JayHodny_2-1751378698767.png

Cultivar is present but our arborist has not requested this field.

We plan to use Field Maps forms to collect the data, assuming we can get this taxonomy workflow working.

Any help would be greatly appreciated, thanks in advance.  Regards, Jay

 

 

 

0 Kudos
1 Solution

Accepted Solutions
JenniferCadkin
Esri Contributor

@JayHodny 

Each Attribute table has an option to auto update when there is only one possible option.  It is accessed from the burger button at the top right of the table.  The option is per table and is honored when modifying values in the Attribute table and in the Attributes pane.  

 

JenniferCadkin_0-1751473182896.png

 

The error is showing because the Contingent Attribute Value Field Group is marked as restrictive.  A couple options to avoid this: 

1.  Change the Contingent Attribute Value Field Group schema from Restrictive to optional

2.  Edit required Contingent Attribute Values in the Attributes pane with the Auto-Apply option unchecked- for existing features.

3.  Use the Create Features active template pane to set attributes before creating features

JenniferCadkin_1-1751473659981.png

 

View solution in original post

0 Kudos
2 Replies
JenniferCadkin
Esri Contributor

@JayHodny 

Each Attribute table has an option to auto update when there is only one possible option.  It is accessed from the burger button at the top right of the table.  The option is per table and is honored when modifying values in the Attribute table and in the Attributes pane.  

 

JenniferCadkin_0-1751473182896.png

 

The error is showing because the Contingent Attribute Value Field Group is marked as restrictive.  A couple options to avoid this: 

1.  Change the Contingent Attribute Value Field Group schema from Restrictive to optional

2.  Edit required Contingent Attribute Values in the Attributes pane with the Auto-Apply option unchecked- for existing features.

3.  Use the Create Features active template pane to set attributes before creating features

JenniferCadkin_1-1751473659981.png

 

0 Kudos
JayHodny
Frequent Contributor

Hi Jennifer,

Many thanks for the reply and the help.  I may have misinterpreted the "Restrictive" setting initially, so I unchecked that option.  Now the Create Attribute pane is showing subsequent taxonomy choices based on the 'common name' I select.  Next, I clicked on the 'Contingency Values....Auto-update other fields.'  When I create a tree feature using the Create Features pane, I choose the common name, and woohoo, the subsequent taxonomy values populate!  I hope that when I publish the layer to an ArcGIS Online editable service this functionality is available in the service layer in my web map in Field Maps.  Time to find out!

Thanks again, Jay

 

JayHodny_0-1751901628137.png

 

0 Kudos