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; } } }

Contingent values not pushing from Pro to Field Maps

PaulPetersen1

I am attempting to use contingent values in Field Maps from a hosted feature service within the AGO environment. I've set up the contingent values in ArcGIS Pro 2.9.3, and everything seems to be working fine in the Pro environment. However, when I publish to hosted feature service in AGO and then test in Field Maps, it reverts to the full domains, rather than the contingent values. I was under the impression that if I set it up in Pro, it should just "work" once I publish to AGO. Am I missing something?

When I look at the REST endpoint of the layer, Has Contingent Values = True. So that looks okay, but it's not propogating to the webmap or Field Maps.

Vind meer berichten getagd met

Accepted answers

PaulPetersen1

Ok, I got it figured out. Once I eliminated any contingent value with the double quote inch symbol ("), then it worked. So the issue was not limited to the quantity of contingent values, but apparently it was blowing up due to the (") symbol.

Not sure if this is a bug or a known limitation.

All comments

PaulPetersen1

Update: I trimmed down my list of contingent values from ~270 down to about 20, then republished. Then Field Maps worked perfectly. Is there some sort of limitation in the number of contingent values within a given field group that can be supported in AGO? Again, it works just fine in Pro with the full list.

PaulPetersen1

Not sure if this is a bug or a known limitation.

ShannonJ

I'm having a similar issue where my contingent values aren't pushing to field maps. I have no ' " ' in any domains, I did have a ' : ' and ' / ' which I deleted, and republished and still got the same issue. I was so excited when I found contingent values but I feel like I'm missing a step somewhere.

when I look at the REST services directory it says that the feature has contingent values and they work in editing in the webmap viewer.

PaulPetersen1

Have you tried updating your version of Field Maps? If you're still on an older version on the mobile device, that would explain why it works in the web map, but not in the Field Maps app.

ShannonJ

We are up to date on the devices I have been testing with

Doe mee aan het gesprek

Aangemelde leden kunnen berichten plaatsen, updates volgen en meer. Nieuw hier? Registreer een gratis account.

Snelle Links

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