Field Maps error "Geodatbase field not found"

[GIS_System_AdministratorSunshi]

I have got a published feature service (MXD 10.8.1) with a handful of layers. One of the layers is not validating in Field Maps. Also is not visible in Collector. But works in Collector Classic. 

is visible in AGOL map.

The error I get in Field Maps say Geodatabase field not found"

It is a point layer, with attachments. Simple symbology. 

When I take the one point layer and publish it in a blank MXD by itself. It works. 

I have tried a blank MXD and copied all the layers from the original MXD across. republished as feature service. No luck. Still doesnt draw in Collector or Field Maps.

Hoping someone can shed some light on the error message given in Field Maps "Geodatabase field not found"

Shape field is turned on, editor tracking is enabled, globalID and ObjectID are visible

Thanks

[Anonymous User]

Did you ever find the cause for this or a solution? We have recently received this error, along with "geodatabase is full". However, the errors are random in occurrence and "resolve" themselves without us doing anything different. We are also working with offline map areas, in case you were not. Packaging, download, and syncing all complete with no errors. 

[RadhakrishnanNeelakantan]

We also got similar error. The webmap with the feature service layer is working fine from Collector, but Field map refuses to load the layer saying "Geodatabase field not found"

If you have found the solution, please let us know.

[AndreasB]

Any answers regarding this issue?

[Jefcoat_Nathan]

Yes, I was able resolve the issue.  The layer that was causing problems was a view layer.  I recreated it but that did not fix the issue.  However, there were other view layers created from the same parent layer from the feature service that had thrown the error.  I recreated all the view layers and that seems to have solved the issue.  

[Jefcoat_Nathan]

I have also just had this occur out of no where.  

[AndreasB]

Did you have any luck already on solving this issue? 

[Anonymous User]

We have a "fix". It was a lot of trial and error, but we originally got this error in Field Maps sporadically. The webmap contained a feature service that was published from ArcMap. We republished the service using ArcGIS Pro. It has been over a month and we have not received this error since the overwrite. I'd say if you are using services that were published from ArcMap, it is worth a try to publish from ArcGIS Pro. 

[RadhakrishnanNeelakantan]

Thanks for posting the fix