invalid column names in Field Maps

[Gisbert61]

I have this 4000+ record  hosted feature class which had some redundant, unused and surplus columns, which I deleted using Pro.

After that I created a form using field maps designer. It all seems ok until you use Field Maps and try to submit a new entry which doesn't work with an "Unable to submit, 1 or more attributes failed"

In the newest Field Maps the logging is improved so I the errormessage is: 

1/10/25, 15:46:03 [EDITING] stopEditing failed with error: applyEditsError(Optional(ArcGIS.ServiceError(code: 1000, description: "Service error code 1000", details: "Invalid column name \'Hoogte_s\'.\r\nInvalid column name \'Len_B\'.\r\nInvalid column name \'DBH_op_1_s\'.\r\nInvalid column name \'DBH_op_2_s\'.", info: [:])))

And those are (some of) the columns I removed so that is at least more info.

Now my question is how to get rid of this error? I tried removing the layer from the webmap, saving the webmap, adding the layer to the webmap and recreating the form but that does not change anything.

I understand the form is stored in the feature layer so I gather there is an outdated schema somewhere, when looking at the data tab in Online I don't see 'old' columns.

Thanks in advance for your time.

Bert Kraan

[CodyPatterson]

Hey @Gisbert61 

Is this happening to only you or others? You may need to clear the app cache by uninstalling and reinstalling the app. I've had an upgrade from 11.2 to 11.3 do this to me, and it really only affected me, other users were fine but a reinstallation did it just fine strangely! The web map is probably fine in my mind, have you tried attaching this layer to another separate web map and observed any issues?

Cody

[Gisbert61]

Hey @CodyPatterson,

This is happening to multiple (all) users, iPhone (SE) and Android(15). Uninstalling and reinstalling the app didn't work on my Android and iPhone.

I have the same issue on a iPad mini(a17 pro) which runs iOS 18.2.1, 

Creating a new map with this layer does not help, the issue remains the same. Dutch support asked me to check if the popup or form shows deleted fields but that is not the case.

The only reference to the deleted fields is in the logging of the field maps.

[Gisbert61]

Newest info: when exported as a filegeodatabase and deployed as a hosted feature layer I can see 29 fields when looking at the feature layer - data tab. That seems ok, but when I enter that layer in a webmap and look at the fields with the formsbuilder of field maps designer I see only 19 fields.

Some of those fields have been previously deleted, but somehow still visible. Also i don't see some of the fields that show up in  the data tab of the layer.

formsbuilder:

fields in the data tab:

So, that is something I didn't expect. Anyone any idea?

I read somewhere the form is stored with the feature, ss there a way to strip the form completely from the feature?

And  to make things even more eerie: Yesterday afternoon I repeated the whole process: unzip the downloaded geodatabase, load the feature, share it to online (using a different name) and exactly the same happened (no surprise there)

BUT

this morning that feature layer showed 22 fields ... no outdated fields and the new fields visible.

Is there some sort of caching somewhere in ArcGIS Online? I'm the only one with admin rights in our organization. Could a fieldworker have caused this by trying to submit a record?

Confused,

Thanks for your time.

Bert 

[Gisbert61 · Accepted solution]

UPDATE: I have a working form in the feature layer, so the case can be closed.

long story short: exported the faulty hfl as a geodatabase, downloaded it, opened in Pro (deleted the faulty layer from Online. shared the downloaded fl to online and recreated the form. Kudo's to Dutch servicedesk!

As I saw the correct field this morning (which were definitely not visible yesterday) I created a form which worked so the workers are happy once more.

But the question remains why this happened in the first place. I don't have a CDN or other form of caching. My IT guys swear they don't cache anything on their side...

Keep safe everyone.