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

Best practice for editing contingent values

MikeFiguray

Hello,

What would be the best practice currently for updating contingent values on a hosted feature service? I missed a contingent value in a project I'm working on, and I need to get it in the project.

In ArcGIS Pro, when I open from the portal or download the ".pitemx file" from the item details page, the contingent values tool is read only and I am unable to update.

If I Download the FGDB into Pro, the existing contingent values no longer exist. I'm also worried that if I recreate the contingent values in Pro and overwrite the feature service, I'll need to start from scratch on the smart forms which is far from ideal.

Is there a way to use ArcGIS Online Assistant or some other online tool to update existing contingent values, or do I just need to bite the bullet and overwrite the existing layer?

Thanks for any info!
Mike

Vind meer berichten getagd met

Accepted answers

JustinReynolds

I think you will have to republish the service since the contingent values are managed server side. However, you do have options on how to preserve the form. Here is a link to a blog that provides some details on that.

https://www.esri.com/arcgis-blog/products/field-maps/field-mobility/duplicate-maps-and-forms-for-use-in-field-maps/

All comments

JustinReynolds

MikeFiguray

Thanks Justin! That helps a lot! Was really hoping not to rebuild the form! I think I remember reading that editing conditional values and attribute rules will be coming to AGOL relatively soon too, so that will be nice.

Thank you,
Mike

KevinBurke

Hi @MikeFiguray and @JustinReynolds

There is a known issue with ArcGIS Online regarding the contingent value definitions not being added to the exported File GDB from the hosted feature service. Therefore once that gets addressed, that workflow should work successfully.

Thank you

-Kevin

ChrisH2

Wondering if anyone has any updates on how to approach this?

I have the same issue as the OP where my contingent values are subject to change a little (within the existing contingent groups) and republishing via Pro is quite time consuming. My source GDB has a poly featureclass and a related table, both of which utilise contingent values. Republishing requires me to download data from the FS and reinsert into my source GDB (as the portal FGDB downloads don't include relationships) and quite a bit of mucking around and checking

SMauri

I'm having the same issue. In my case, I also have updates to the contingent value table which would force me to download the data from ArcGIS Online, update the do mains associated with the fields, and the contingent value mapping table itself.

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.