Enterprise user logs Deleted polygons

[BjorntenBroeke]

Hi All, 

We have a the complete Enterprise environment with a Postgres Database, with an Portal access where users can change and edit Polygons and Points in the field. 

Whe Publish teh Polygons and Points Both in two seperate Feature Layers (not hosted). Our issue is that we need to log wo deleted a polygon.

When I export a Report, form Portal/Organization/Status/Reports I can only export a Item listing. My hopes was that there was some information about who deleted polygons. 

Is there any best practice to Publish a Polygon or Point layer, and then setup the loggin. 

I reading a few articiles about setting up the Feature Class with Versioning (Batch) and Archiving. Does that help, and give me the option the generate a Log file whom deleted polygons?

Hope somedody can help me here. 

Bjorn 

[Reinaldo_Cartagena]

Hi Bjorn,

Archiving provides the functionality to record and access changes made to all or a subset of data in a geodatabase. Archiving is the mechanism for capturing, managing, and analyzing data change over time.

A simple way is to implement is the history of changes. See the following link:

https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview/what-is-archiving-.htm 

Reinaldo.

[Reinaldo_Cartagena]

Hi Bjorn,

In multiuser editing scenarios, versions allow editors to work with the same data at the same time without applying locks or duplicating data by giving each editor their own unique, isolated view of the data. Versioning facilitates long transactions by allowing editors to work isolated within their own version of the geodatabase and across multiple edit sessions. Once an editor finishes a collection of edits, they can merge their changes back to the parent version from which their version was created. The original parent of all versions in a geodatabase is called the default version.

Another easy way is to implement editing over versions. See the following link:

https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview/overview-of-versioning-in-a... 

Reinaldo.

[Reinaldo_Cartagena]

Various workflows require you to distribute your data to different geodatabases and synchronize changes made to the data in each geodatabase. The following provides a guide to help you determine how best to use distributed data, geodatabase replicas, and synchronization for your system. Another easy way is to implement geodatabase replication. See the following link:

https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview/geodatabase-replication-fun...