Select to view content in your preferred language

Feature Service Edits Don't Actually Save, No error message

200
0
a week ago
Labels (3)
SarahFrost
Emerging Contributor

My organization recently moved away from direct connections to our SDE for feature class editing, to using feature services published to our Enterprise and added to our AGOL as secured items. An issue we're facing and unsure about the root of is edits not saving. It's sporadic across users, with no detected pattern. Users bring the service into Pro, make edits using the Attributes Pane or within the Attribute Table, and Save edits within the Edit ribbon. It's just editing attributes; not geometry, and not running tools.

From there, the edits initially seem present within the service from within Pro, but here's what's odd:

  • When refreshing applications that consume this service, the edits are not present
  • When saving the Pro project and reopening, the edits are no longer present in the data
  • When checking Manager logs, neither Info nor Debug messages show genuine communication between the user and the service. As in, there are no messages whatsoever, as though the user never made an edit or even brought the service into a Pro project. 

What is especially concerning is the lack of error messages. All edits seem to go through (in that Saving within the Edit ribbon in Pro generates no errors), but in reality only some do, and some don't, with no way to tell aside from manual checking of every edit.

Many thanks for any insight!

0 Kudos
0 Replies