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

can not get update data to work--no field names for match appear

JayLarsen

I am trying to use the "Update Data" feature in AGOL.

I have a feature layer with a few mundane fields. I just wan to update and add new features.

As I walk thru the "Update Data" process it is all going well until I hit the screen where you must tell it what field to use as the key field to match. Both dropdown menus for the orig layer and update file show only "none" and "FID". Neither of which work. Why are none of the fields showing up for either file?

What is the secret?

Update file is just an excel file with one tab in it that contains the data.

Vind meer berichten getagd met

Content Management

Data and services

Mapping

Accepted answers

bbollin

@JayLarsen Yes I have! So the advice I gave was for unique ID matching but it sounds like you're having more trouble on the field matching page. I'd have to take a close look at your data as well to understand what is happening. It's also possible that the excel file has fields formatted differently (for example, it might save a number column as text, which means you cannot match it up with any numerical fields in arcgis online. Can you send a screenshot of the field types in the ArcGIS online hosted feature layer and the fields in the excel file?

All comments

bbollin

hi @JayLarsen, you have to have fields with unique values only to show up in the id matching drop down. You can set this by going into the data tab -> opening the field details you want -> changing this setting to requires unique values

JayLarsen

Not what my tech support case person said...but interesting idea.

Have you done an update/append or update & append operation in AGOL successfully?

bbollin

JayLarsen

Whoo hoo!!! That was the trick! Designating one of the name fields as "unique" allows it to show up in the dialog for matching!!! Fortunately, I've designed most layers with a unique name or nickname setup, so setting the flag for the field allows the process to work.

How did I not know this? I guess I rarely use the metadata types on fields, and many of my layers are old. Also, many times I re-design layers for major updates rather than try to update...but updating will be much more typical now as my designs have matured.

THANKS!!!

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.