topic Re: Bug with arcpy.management.EnableEditorTracking on Enterprise 10.9.1 in ArcGIS Enterprise Questions

Bug with arcpy.management.EnableEditorTracking on Enterprise 10.9.1

MaximeDemers — Mon, 18 Nov 2024 19:27:52 GMT

Hello,

I encounter a bug when I use arcpy.management.EnableEditorTracking on ArcGIS Enterprise 10.9.1 (not ArcGIS Pro)

The method seems to not support the None value for the fields parameters:

import arcpy, os FC = os.path.join(r"\\server", "my_database.sde", "my_feature_class") arcpy.management.EnableEditorTracking( in_dataset = FC, creator_field = None, creation_date_field = None, last_editor_field = None, last_edit_date_field = "et_last_edit_date", add_fields = "ADD_FIELDS", record_dates_in = "UTC" )

As we can see in the screenshot, the et_last_edit_date field is applied to the creator field (Champ d'auteur in french) not the last edit date field as it is specified in the code above.

Re: Bug with arcpy.management.EnableEditorTracking on Enterprise 10.9.1

JesseCloutier — Tue, 19 Nov 2024 13:52:11 GMT

Hi @MaximeDemers, we appreciate you sharing a potential bug with the broader Esri Community; however, Esri does not actively track software defects posted here. The official channel for investigating and validating bugs is Esri Technical Support. All customers experiencing a potential software bug should leverage technical support to report and investigate the issue.

By reporting bugs through technical support, Esri can better track the scope and impact of the issue across all our customers and better prioritize it with our product teams. Our teams can also investigate the issue more thoroughly to see if there is a solution, workaround, or patch to get you back up and running as soon as possible.

As a reminder, Esri Community is primarily a self-service support platform where Esri users can ask or answer each other’s questions, share feature requests, and collaborate to solve problems with GIS.

*Note that this is a scripted message prompted when posts allude to a potential product bug.

Re: Bug with arcpy.management.EnableEditorTracking on Enterprise 10.9.1

MaximeDemers — Tue, 19 Nov 2024 14:06:25 GMT

@JesseCloutier

Maybe Esri should have a simple platform to submit bugs like on github. I would like to help Esri improve their product but I dont have time to call the technical support.

Re: Bug with arcpy.management.EnableEditorTracking on Enterprise 10.9.1

ChristianWells — Mon, 25 Nov 2024 17:11:39 GMT

Hi @MaximeDemers - the keywords you are using 'None' for are optional and should only be used if you have a pre-existing field in your dataset that you want the tool to use instead of the default values the tool will create. I don't believe this to be a bug, if you can remove those three keywords from your script, it should run successfully.

Re: Bug with arcpy.management.EnableEditorTracking on Enterprise 10.9.1

MaximeDemers — Mon, 25 Nov 2024 19:13:58 GMT

Hi @ChristianWells ,

Thank you for taking the time with this. Unfortunately, what you suggest does not solve the problem with the arcpy.management.EnableEditorTracking

The script just not works when I remove the unused parameters.

arcpy.management.EnableEditorTracking( in_dataset = FC, last_edit_date_field = "et_last_edit_date", add_fields = "ADD_FIELDS", record_dates_in = "UTC" )

arcgisscripting.ExecuteError: ERROR 001215: Enable editor tracking skipped for field: et_last_edit_date.

I have tried all possibles parameters combinations and there is no way to make the function enable tracking editor only for the last modified date field.