nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Import Contingency Values

OliverIshmael

I am using ArcGIS Pro 2.9.6 and am trying to import a Field Group and Contingency Values using the Import button on the ribbon:

To the import dialog box, I have added my Field Group.csv which looks like this:

and I have added my CV.csv which looks like this:

When i click OK it results in this error:

Is this a bug / How do i resolve this?

Find more posts tagged with

Geodatabase

Desktop

Accepted answers

Robert LeClair

@OliverIshmael - so in reviewing a support case from a customer, they were experiencing the same thing as you. The way they resolved the issue was calculating the SUBTYPE field to be zero's for all rows in the *.csv file if there was no subtype to begin with in the feature class. Then the Import Contingent Values GP tool should work.

All comments

Robert LeClair

@OliverIshmael - there was a BUG-000156170 - Contingent values are not listed correctly in ArcGIS Field Map as they are not categorized by Recommended and Other. The workflow was working properly at 22.3.0 where it would display a listed a recommended values being returned. At Field Maps for Android 23.1.1, iOS 22.42 and 23.1.1 it would throw an error.

Response from the internals is "Fields and contingent field groups within the layer or table can be added to the form and configured as form elements. Once fields are added, they can be configured on how to appear on the form. If a field includes a list of values, there are further instructions in the ArcGIS Field Maps Help documentation: https://doc.arcgis.com/en/field-maps/android/help/configure-the-form.htm"

I don't specialize in ArcGIS Field Maps so it may be worth a call to Esri Support Services.

OliverIshmael

@Robert_LeClair I was unable to resolve the issue with the Field Group, so i manually input the exact same values and this appeared to resolve the problem, in that each row was marked temporarily by a green square (as opposed to a red one as seen in the image above). This seems to imply that there is a problem with the bulk important tool.

Upon testing in Field Maps, the contingent values still do not work - On the Hazards form all values are shown irrespective of prior field group choices; The Location_Facilities values should filter based on the Location_Site value selected, but this does not occur. In the attached screenshot (unfiltered facilities.jpg) from Field Maps, the Site: 'MtB trail - Beast - Visitor centre car park' has been selected, but when the list of Facilities is displayed they have not been filtered (the values that are prefixed 'Beast' are the only ones that should show). Meanwhile, on the Assets form the list of Facilities is being filtered correctly, however, when i select a value - Field Maps displays an error saying that the 'Value combination is invalid' (see relevant .jpg). Can you identify why this is happening?

Another issue is that the contingent values for a field are not displayed in the order i added them or indeed alphabetically, which makes searching them difficult. I have overcome this by prefixing the name of the facility with a reference to the Site (see attached jpg). Is there is a way to address this?

Field_Group_v2.csv

CV_v2.csv

unfiltered facilities.jpg

Value combination is invalid.jpg

Robert LeClair

@OliverIshmael - great to hear that my response fixed the initial problem you were experiencing. With regard to your 2nd error, I searched the internals and a customer who had the same error message discovered they had a duplicate contingent value and used the Remove Contingent Value (Data Management) tool to clear it. This resolved the error message.

OliverIshmael

@Robert_LeClair That fixed the problem and let me bulk import the contingent values, however, ArcPro now reports that it has "Found contingent value error for field group: Location_group"

It is not clear what the error is - can you spot any potential issues from the included screenshots?

Robert LeClair

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.