Latest Contributions by KenGalliher1

‎10-27-2025

Can you try with the latest version of the Python API (2.4.2)? The `folder.add` method returns a `Job` object. The `Job` object has the `done` method to allow for polling of the upload status and the `result()` method to retrieve the `Item`. arcgis.gis module | ArcGIS API for Python | Esri Developer

‎10-20-2025

Adding to the response from @Clubdebambos : This was fixed to allow for long url strings to be properly decoded in a GET request. The fix can be found in the 2.4.1.3 patch and the latest 2.4.2 release.

‎08-25-2025

@IsakL The documentation page will be updated with samples. The `ContentManger.folder.core.Job` class will have a result method. # Usage Example: Getting item resulting from a job from arcgis.gis import GIS, ItemTypeEnum, ItemProperties gis = GIS(profile="your_online_profile") csv_file_path = "/path/to/your/data.csv" new_data_item_job = gis_folder.add( item_properties=ItemProperties( title="new_source_csv_item", item_type=ItemTypeEnum.CSV, snippet="A new csv item.", description="CSV data item added through a folder add.", tags=["csv_item", "gis_data"] ), file=csv_file_path ) if not new_data_item_job.done(): print("... job processing...") else: csv_item = new_data_item_job.result() csv_item <Item title:"new_source_csv_item" type:CSV owner:online_data_owner>

‎08-15-2025

Hi @IsakL You're right, the documentation is not accurate. This has been addressed and will be available in the next release. The server is returning a job and the Python API has begun taking advantage of that. The `folder.core.Job` object that is now being returned has the `result` method which will return the added `Item`. item_props = ItemProperties( title="new_shapefile_item", item_type=ItemTypeEnum.SHAPEFILE.value, tags=["tag1"], snippet="Demo item added from Python API", ) add_job = folder.add( item_properties=item_props, file=r"E:\data\some_lines.zip" ) print(type(add_job)) print(add_job.result()) # >>> <class 'arcgis.gis._impl._content_manager.folder.core.Job'> # >>> <Item title:"new_shapefile_item" type:Shapefile owner:my_username>

‎01-31-2025

What version of Pro and Python API are you using? Some changes went in last August that help the API better manage version locking.

‎01-31-2025

Give one or both of these a try: When using the Version object, use the context manager with the "read" argument, then set the mode to "edit" inside. This will help manage the starting and stopping of the edit session automatically. The initial "read" session will acquire shared locks on the version and "edit" will apply the exclusive locks. with version_mgr.get(version_name, "read") as version: version.mode = "edit" res = version.edit(fl, updates=edit_feature) print(res) Usually (not always) the error "Object has no schema locks" means the edit session either didn't start or there is an old edit session still open. You are using purgeLock to fix that which is correct. The error "Cannot acquire a lock" means there is an open edit session. This is where the context manager should help. Upon exiting, it should stop any open read and/or edit sessions with that session ID. Alternatively, try using the edit_features method in the FeatureLayer object by passing in the version name string. fl.edit_features(updates=[edit_feature], gdb_version="owner.version_name") Editing Features | ArcGIS API for Python

‎09-13-2024

Hello, Adding a new field to a published feature class will require a few things. These can be done through the server manager web page. Uncheck the Lock Database Schema option. Go to your service and then the Parameters section. Click Save and Restart (this is a service level change and requires a restart) Go to your feature class and add/update any fields or any other type of schema change needed. Add the parcel fabric to a map and go to Share > Overwrite Existing Service Once the service is finished overwriting, go back to the Parameters page and check back on the Lock Database Schema option. Save and Restart the service again. Adding a new field(s) and adding new parcel types to a parcel fabric is considered a schema change and requires the service to be republished or overwritten. Changes to service options such as adding capabilities or in this case unlocking the schema are considered service level changes and only require restarting. For more information, see our Data Management Meetup video here: Meetup: Parcel Fabric Data Management - Esri Community

‎07-12-2024

If you decide to go the join route with SQL, as @jcarlson mentioned above, querying branch versioned features requires some extra logic. See the link below describing how to join an outside table to a parcel type feature class. The Records feature class can be used instead. Once the structure of the join is built, the result can be further filtered on a date. -- Filter from sub result set AND a.RetiredByRecord IS NULL AND a.IsSeed <> 1 AND a.create_date = '2023-07-13 16:12:55.473' Query Branch Versioned Parcels - Esri Community

‎05-21-2024

Hi Matthew, When the option is checked, the layer IDs should never change. Let me know if you're seeing something different. On the other hand, if you uncheck the "Ensure map is set to allow assignment of unique IDs" option, you then have the ability to assign your own Assign layer IDs—ArcGIS Pro | Documentation To answer your question: But I can't just overwrite with the new layer, because that would break maps that used that layer, right? Yes, it would be possible that maps and any scripts or custom applications that rely on a specific layer ID could break.

‎05-17-2024

Hi Matthew, You'll want to ensure that during publishing, the "Allow assignment of unique numeric IDs" option is checked. From Pro, that option is in the map properties When analyzing the publishing of the service, this unique ID option is flagged as an error unless the following option is unchecked.

‎05-17-2024

Hi Matthew, There's a somewhat hidden option that needs to be handled before adding the parcel type to an already published fabric. In the Server Manager > Parameters page, uncheck the Lock Database Schema option. Here are the steps I would suggest if the service is currently at its original starting point. Go to Server Manager > Parameters and uncheck the Lock Database Schema Option Click save and restart (this is a service level change that requires restarting) Run the Add Parcel Type geoprocessing tool Register the feature dataset as branch versioned again. Add all the new feature classes to the map you want to publish Share the map by overwriting the existing published service (or publish a new service) Re-check the Lock Database Schema option Restart the service again Let me know if that helps.

‎02-12-2024

Hi Ofir, This is a known issue with the Change Version GP tool and we are working on fixing it in an upcoming release. This will help change the version for all container datasets and their associated layers (Parcel Fabric, Utility Network, etc.). In the meantime, we have found success using the ArcGIS Python API to access version information and loop through each layer in the map to change its properties. See this post specifically Thanks, Ken

‎01-25-2024

Released with Pro 3.2 is the ability to read and update the active parcel record in a map containing a parcel fabric. Using ArcPy CIM Access, this set of properties will allow users to automate: Discovery of a map’s active record. To set a new active record. Activate/deactivate the active record. Toggle the visibility of features in the active record. The Cartographic Information Model (CIM) provides access to many settings and properties of ArcGIS Pro that may not have a publicly exposed API through the ArcPy.mp module. Starting at Pro 3.2, the CIM now contains the following properties: Type Property Description Bool isParcelFabricLayer Denotes the layer is of type ParcelFabricLayer String activeRecord The GlobalID value of the active record (if set) Bool enabled Is the parcel record set in the current map? (True | False) Bool showActiveRecordOnly Should the map only display features participating in the active record A typical workflow may be: Access a Pro project and map with arcpy.mp Determine if a map has a parcel fabric. If a parcel fabric layer is in the map, determine if there is an active record. If no active record, set the record with a known GUID of an existing record. Set the record status to “enabled”. Optionally, set to display only the parcel features associated to the now active record. # Full script for Python Window. # Replace "CURRENT" with path to target Pro Project to run outside of Pro # access the project and map current_project = arcpy.mp.ArcGISProject("CURRENT") target_map = current_project.listMaps()[0] print(target_map.name) # test the parcel fabric exists by its name map_layers = target_map.listLayers() parcel_layer = [lyr for lyr in map_layers if lyr.isParcelFabricLayer][0] # if the parcel fabric exists, check for the parcelFabricActiveRecord property if parcel_layer: # get current CIM object parcel_cim_def = parcel_layer.getDefinition("v3") # if the active record is not set, set it. if not parcel_cim_def.parcelFabricActiveRecord.activeRecord: # Set the new values parcel_cim_def.parcelFabricActiveRecord.activeRecord = "6B1431DA-1D9B-4B69-BD24-79EB643D8C98" parcel_cim_def.parcelFabricActiveRecord.enabled = True parcel_cim_def.parcelFabricActiveRecord.showActiveRecordOnly = True # save the CIM definition, save project, open the map (optional) parcel_layer.setDefinition(parcel_cim_def) current_project.save() target_map.openView()

‎01-11-2024

Ah, OK. According to the error, the feature classes are registered as versioned but the connection file is not set to Branch. 00264: Branch versioned dataset, <value>, is not supported from a versioned workspace when the service is editable—ArcGIS Pro | Documentation Right click the .sde file and choose Geodatabase Connection Properties There should be an option for Branch versioning. Select Branch Re-add the fabric to the map

‎01-11-2024

The best thing to do at this point is to run the analyzer. It will of course tell you that Branch Versioning is not set, but it should give clues as to why. Some things to check when the Branch Versioning option is missing: 1. Make sure the fabric feature dataset was registered as versioned. 2. Is the geodatabase connection file set to Branch? Right click the .sde file and choose Geodatabase Connection Properties There should be an option for Branch versioning If this was the issue, check the option on and re-add your fabric to the map 3. The Validation or other layers and tables were not registered as versioned. Perhaps the parcel fabric is registered correctly but something else isn't. This could be the 3 validation layers and its associated table. Some other supporting layer that is outside of the feature dataset. Run the analyzer and let us know what it reports. Thanks!

Online Status	Offline
Date Last Visited	a week ago

My Ideas

Latest Contributions by KenGalliher1

Re: Folder.add() no longer always returns a Future object?

Re: FeatureLayer::query() - Force HTTP POST instead of GET?

Re: Folder.add() no longer always returns a Future object?

Re: Folder.add() no longer always returns a Future object?

Re: Updating Branch Versioned Feature Layer Fails w/ Lock Acquisition Exception

Re: Updating Branch Versioned Feature Layer Fails w/ Lock Acquisition Exception

Re: Is there a workflow documented for adding a field to an already published parcel fabric?

Re: arcgis parcel fabric year wise active parcel view

Re: How do you add a parcel type to a parcel fabric that is published on portal?

Re: How do you add a parcel type to a parcel fabric that is published on portal?

Re: How do you add a parcel type to a parcel fabric that is published on portal?

Re: Problems with Arcp3.2 Parcel Fabric Using ArcPy to Change the Version

Parcel Fabric Active Record Automation

Re: Publish the parcel fabric as a feature service missing properties

Re: Publish the parcel fabric as a feature service missing properties

Re: Issue converting H3 cell boundary WKT to geome...

Re: FeatureLayerCollection.replicas.create always ...

Re: Issue converting H3 cell boundary WKT to geome...

Re: A Special Thanks to the ArcGIS API for Python ...

A Special Thanks to the ArcGIS API for Python Comm...