Latest Contributions by NanaDei

Hi @KevinPiraino2 , the Prune Branch History geoprocessing tool supports parcel fabric datasets starting with the ArcGIS Pro 3.7 release. Review the following documentation on the usage requirements. ... View more

This request has been addressed in the ArcGIS Pro 3.6 / ArcGIS Enterprise 12.0 and later releases. For example, review the enterprise geodatabase in PostgreSQL documentation for information on the size and name limits. ... View more

Thanks @RClavero . Yes, work is underway to extend support for additional authentication options, starting with key-pair authentication this year. Please create ideas for other authentication options with any specific security policies, if you are looking to use it in ArcGIS Pro and ArcGIS Enterprise. ... View more

Unfortunately, we don’t have an estimated timeline at the moment. I’ll reach out to learn more about your current use of Snowflake with ArcGIS and the authentication methods being used. ... View more

Yes, we plan to extend support for additional authentication types including key pair. ... View more

There are plans to support GeoParquet in ArcGIS Pro. As you noted, GeoParquet isn't supported with the Multifile Feature Connection. I'll send you a message for us to coordinate and obtain the two GeoParquet files for review. ... View more

Thanks @JTessier, the goal can be achieved by authoring a constraint attribute rule as mentioned in the link you shared. ... View more

ArcGIS Enterprise Workgroup is being phased out with ArcMap. The ArcGIS Enterprise 11.1 release was the last to support the Workgroup license. Please review the following knowledge base article for related information on this topic: https://support.esri.com/en-us/knowledge-base/how-to-apply-a-full-arcgis-enterprise-license-to-arcgis-000028255 As @MarceloMarques mentioned, please reach out to your Account Manager on migrating from ArcGIS Enterprise Workgroup. The bottom section of the above article also sheds light on options for migrating workgroup geodatabases to an enterprise geodatabase. ... View more

Related documentation:  https://desktop.arcgis.com/en/system-requirements/10.7/database-requirements-oracle.htm ... View more

It is not recommended to store locators in a geodatabase. The ArcGIS 10.4 release was the last to support storing locators in a geodatabase. Related documentation: https://desktop.arcgis.com/en/arcmap/latest/manage-data/geocoding/creating-an-address-locator.htm# "Locators should be stored in a file folder so you take advantage of new features that are not supported for locators stored in geodatabases, such as performance improvements, multithreading capabilities, and suggestions support. ArcGIS 10.4 is the last release to support storing locators in geodatabases."   Rebuilding address locators can be achieved through python, and the following blog can be reviewed to schedule python scripts. https://www.esri.com/arcgis-blog/products/arcgis-pro/analytics/schedule-a-python-script-or-model-to-run-at-a-prescribed-time-2019-update/ ... View more

Hi @junaidjawaid , do you have ArcFM installed on the machine that  is running the arcpy script? It seems the script may be modifying data so the Object Reader wouldn't help in this case. You can also check with ArcFM support to determine whether there's a way to achieve the goal. ... View more