Latest Contributions by KenGalliher1

‎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!

‎12-15-2023

Hi @RobertChaney To recalculate the extents in a feature service (published) parcel fabric, the service needs to be stopped and the geoprocessing tool run on the enterprise geodatabase feature classes. The service can then be started and the new extents should be reflected immediately. This can be done with a short arcpy script: import arcpy from arcpy import env gdb = r"/path/to/enterprise/geodatabase.sde" env.workspace = gdb fds = "fabric_feature_dataset" for fc in arcpy.ListFeatureClasses(feature_dataset=fds): arcpy.RecalculateFeatureClassExtent_management(fc) Regarding the "calculating extent" popup, there might be something more going on. I would suggest opening a support case where they can take a look.

‎12-08-2023

For branch versioned feature classes, the version differences can be found with the REST API. This was implicitly mentioned here with the ArcGIS Pro .NET SDK using the Differences method. Differences—ArcGIS REST APIs | ArcGIS Developers It is also possible to retrieve the differences with the ArcGIS Python API arcgis.features.managers module | ArcGIS API for Python from arcgis import GIS from arcgis.features._version import VersionManager gis = GIS( "https://server.domain.com/webadaptor/", "user", "password" ) version_manager_url = ("https://server.domain.com/webadaptor/rest/services/FeatureServiceName/VersionManagementServer") version_management_server = VersionManager(version_manager_url , gis) with version_management_server.get("owner.version_name", "read") as version: differnces = version.differences(result_type="features", layers=[15]) ''' Result: { "differences" : [ { "layerId" : long, "inserts" : [ <objectId> ], "updates" : [ <objectId> ], "deletes" : [ <objectId> ] } ], "features" : [ { "layerId" : long, "inserts" : [ { "attributes" : { "OBJECTID" : 581, "SUBTYPE" : 3, . . . "SHAPE.STLength()" : 132.5 }, "geometry" : { "hasZ" : true, "hasM" : true, "paths" : [ . . . ], "success" : <true | false>, '''

‎11-20-2023

Hi Dean, Thanks for bringing this up. I am getting mixed results with different methods. I am not able to reproduce the issue using Pro 3.2 or Pro 3.1.4 from the Python Window with an open map (target_map("CURRENT")) or from a script pointing to the map project. Interestingly, I can reproduce it with a Notebook using an open map (target_map("CURRENT")). To make sure we're on the same page, with the sample code above, are you expecting only the parcel fabric to switch to the version? I believe we determined that we had to iterate through all of the feature layers to change their version. This is my map after targeting only the parcel fabric: UPDATE: I ran the script from the Python window and the parcel fabric and parcel layers all change version. The topology does not:

‎10-31-2023

This session will consist of short and useful data management demos: How to share a subset of parcel data as a live service that is ‘view-only’ using a database view; how to access the parcel fabric logging in the ArcGIS Pro client and on the ArcGIS Enterprise to better understand performance issues; deploying on the cloud and more.

‎08-14-2023

As long as the gisadmin user does not have any elevated permissions you should be able to copy the data. Look out for things like "sysadmin" or "db_owner". Those roles will alter the schema name and cause the error you saw.

‎08-14-2023

Hello, It looks like the gisadmin user may have some elevated privileges. Please try copying the fabric with a database authenticated user that has only basic editing privileges. CREATE FUNCTION CREATE SEQUENCE CREATE TABLE CREATE VIEW Here is the doc describing the enterprise geodatabase user requirements for parcel fabrics: The feature dataset in an enterprise geodatabase must be from a database connection established as a database authenticated user. This user must have database privileges to create content and cannot be an OS-authenticated, the database administrator, or the geodatabase administrator account. The connected user becomes the parcel fabric owner and administrator. Create a parcel fabric—ArcGIS Pro | Documentation Thanks, Ken

Online Status	Offline
Date Last Visited	3 weeks ago

My Ideas

Latest Contributions by KenGalliher1

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: Parcel Fabric Recalculate feature extents\Spatial Index

Re: Add 'Version Changes' to the Versions Toolset

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

Meetup: Parcel Fabric Data Management

Re: Failed to paste. SDE or DBMS admin user cannot create a parcel fabric

Re: Failed to paste. SDE or DBMS admin user cannot create a parcel fabric

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

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

Re: Receiving error "The coordinates or measures a...

Feature Layer This and Feature Service That

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