Latest Contributions by KenGalliher1

‎09-06-2022

Hi Dean. I am seeing some issues using Pro's Python window as well. I'll continue to look into it. In the meantime, can you try the same thing using a Pro Notebook? I am not getting any errors getting the fabric and version manager.

‎09-02-2022

Hello, One suggestion would be to use the ArcGIS API for Python (ArcGIS Python API). This API is designed to work with feature services and contains all the necessary components to work with branch versioned parcel fabrics. I have written a few samples that show how to manage branch versioning, creating parcel records and other parcel fabric functionality. Part 1 - Introduction to Parcel Fabric layers | ArcGIS API for Python Part 2 - Branch Versioning with Parcel Fabric | ArcGIS API for Python Part 3 - Create a New Parcel Record | ArcGIS API for Python In the "Part 3" example, you can see the new version is passed as an argument when creating a new record. All methods that insert, update or delete data from a feature layer have a parameter to pass in a branch version. edit_features(adds=[record_dict], gdb_version=<branch version name>) The ArcGIS Python API can be used with the ArcPy module and any other python packages. Another suggestion, since it seems you are in a Pro map, would be to create an Add-In with the Pro SDK. This can help simplify setting the version and parcel record and persisting those throughout the map session. ProConcepts Parcel Fabric · Esri/arcgis-pro-sdk Wiki (github.com)

‎05-18-2022

Hi Valerie, Does Enterprise geodatabase follow the same version as ArcGIS enterprise? Creating a new geodatabase or upgrading an existing, older geodatabase will set the geodatabase version to match the Enterprise version. ArcGIS Pro does not force the GDB to be at the same release as the Enterprise but publishing the parcel fabric does. The geodatabase can be upgraded using ArcGIS Pro from the geodatabase properties page similar to ArcGIS Desktop. Regarding when to upgrade, as Amir mentioned, if you want to use ArcGIS Pro 2.9, you will need ArcGIS Enterprise 10.9.1. If you cannot upgrade from your current 10.8.1, the parcel fabric will require you stay at Pro 2.6 as shown in the matrix. Here is a suggested upgrade path: 1. Upgrade ArcGIS Enterprise to version 10.9.1 2. Install ArcGIS Pro 2.9 3. Upgrade the geodatabase that will contain the Pro parcel fabric to 10.9.1 or create a new geodatabase with Pro 2.9. 4. Migrate the ArcMap fabric into the 10.9.1 geodatabase. This will create a "version 5" parcel fabric.

‎02-24-2022

Hello, You can manually inspect and delete connections and locks from the sde geodatabase connection. Right click the .sde connection file and choose Properties > Connections then click the "Show connected users and locks" button. This will open up the connections and locks dialog. Choose the Locks tab and locate the lock(s) of the problem version. Select the locks you wish to remove, right click the selection and choose Disconnect Another possible option is to purge the locks using the REST endpoint. Go to the service's VersionManagementServer endpoint and open the purgeLocks page. Please see the documentation for purgeLock before proceeding: Purge Lock—ArcGIS REST APIs | ArcGIS Developers Example: https://server.domain.com/server/rest/services/MyParcelFabric/VersionManagementServer/purgeLock Enter the name of the version as owner.version_name and click purgeLock(POST)

‎02-09-2022

Another suggestion would be to join the Pro and ArcMap polygon tables and create a database view. This view can be filtered by dates, parcel types, branch versions, etc. The feature classes remain editable which essentially updates the view. Here is some more info on querying branch versioned feature classes and creating views. Query Branch Versioned Parcels - Esri Community

‎02-01-2022

Adding an attribute index should only require a connection as the data owner. Is there any other information in the error message?

‎10-21-2021

Interesting. If you can, please log a case with Support. This shouldn't be happening.

‎10-21-2021

Hi Bryn, Update: False alarm. My error came from a different issue. However, staying with the path theme, can you confirm that the same path used the GP tool or model builder is the same path in the script? I was able to reproduce the error by putting my .sde connection file in a path with a very long character length. I know there are technically limitations on path character lengths in Windows, Python and ArcPy but I'm not sure which one(s) is occurring here since it works from the GP tool and Model Builder. My path above is 252 characters long so I don't think my issue is Windows. https://desktop.arcgis.com/en/system-requirements/10.5/os-limits-windows.htm Please try to shorten the inFeatures path length and see if that helps. I'll see if I can find more info.

‎10-13-2021

It looks to me like you're setting the environment workspace to a file geodatabase while working between two enterprise geodatabases. That shouldn't be a problem but, try commenting out that line or set the env.workspace to your inFeatures SDE connection file. arcpy.env.workspace = <inFeatures_connection_file.sde> Also, do you get the same error running the Feature Class to Feature Class geoprocessing tool from Pro? Ken

‎06-22-2021

With the sysadmin role removed, copy in the feature dataset again with that user logged in. In the catalog pane, the new feature dataset should say <database>.GIS_Admin.<fds_name>. From there, try publish again.

‎06-22-2021

Does your GIS_Admin user have the "sysadmin" role applied? If so, take the user out of that role and try to publish again. What might be happening is the user was given an elevated privilege which causes the user to be seen as having the DBO schema. This creates a mismatched schema situation which is perfectly legal in SQL Server but causes problems in the geodatabase.

‎06-22-2021

Hi Matthew, Double check you are logged into the .sde connection file as the "gis_admin" user. It sounds to me the database connection properties are pointing to a user other than the owner of the data. For example I have a fabric owned by "GIS". To publish this fabric, I would need to log in as the GIS user to the database connection. Let me know if that helps or if you have any more questions. Ken

‎05-12-2021

In our "What's New in 2.8" meetup, I demonstrated using a database view to display parcel fabric features joined with an external table. I didn't spend much time on the SQL so check out the code block and link below for examples. Please be aware that INSERT, UPDATE and DELETE functionality is not available. https://github.com/Esri/developer-support/tree/master/arcsde-sql/sql-server/branch-versioning SELECT a.NAME, a.objectid, b.description_, b.address_, b.owner_, a.shape, a.gdb_geomattr_data FROM gis.tax_4 a LEFT JOIN gis.fake_cama b -- keep all parcels (null external rows ok) ON a.name = b.Name -- Start branch versioning magic WHERE a.GDB_ARCHIVE_OID IN ( SELECT GDB_ARCHIVE_OID FROM ( SELECT GDB_ARCHIVE_OID, ROW_NUMBER() OVER( PARTITION BY OBJECTID ORDER BY GDB_FROM_DATE DESC ) AS rn_, GDB_IS_DELETE FROM GIS.TAX_4 WHERE GDB_BRANCH_ID IN (0) AND GDB_FROM_DATE <= GETUTCDATE() AND OBJECTID IN ( SELECT OBJECTID FROM GIS.TAX_4 WHERE (RetiredByRecord IS NULL) ) ) AS br__ WHERE br__.rn_ = 1 AND br__.GDB_IS_DELETE = 0 ) -- End branch versioning magic -- Filter from sub result set AND a.RetiredByRecord IS NULL AND a.IsSeed <> 1

‎09-03-2020

Hi Craig, Can you let me know the following: - SQL Server version (2014, 2017, etc.) - ArcGIS Pro version (2.4, 2.6.1, etc.) - Geodatabase version (10.7, 10.8, etc.) - Version of the parcel fabric being copied in. This can be found in the parcel fabric properties pane. There are a couple of things that jumped out at me in the error message although I can't reproduce the error. The first one is the length of the fully qualified table name. In SQL Server geodatabases, the table name can be 128 characters long but the alias can only be 31. If possible, try a shorter data owner name. Or better, a shorter database name and owner name. Enterprise geodatabase size and name limits—Help | ArcGIS Desktop The username has the word "admin" in it. Make sure there are no elevated database or server privileges associated to that user such as sysadmin or DBO. Create a parcel fabric—ArcGIS Pro | Documentation My last observation is the version of the SQL Server ODBC client. The ODBC 17 client is the latest. Try installing this and copying the fabric again. Download ODBC Driver for SQL Server - SQL Server | Microsoft Docs Thanks, Ken

‎04-01-2020

This zip file contains a Jupyter notebook and a python file that demonstrates using the ArcGIS Python API to merge parcels in a branch versioned feature service.

Online Status	Offline
Date Last Visited	Monday

My Ideas

Latest Contributions by KenGalliher1

Re: Branched Version Parcel Fabric Workflow

Re: Branched Version Parcel Fabric Workflow

Re: Editing Parcel Fabric in an ArcGIS Enterprise environment

Re: Cannot Delete a version - Error 000386 Locked by database user

Re: Scripting a sync process from fabric to traditional parcels feature class

Re: Indexing field in the Parcel Fabric - no permissions?

Re: Export features from Parcel Fabric using Python

Re: Export features from Parcel Fabric using Python

Re: Export features from Parcel Fabric using Python

Re: Problem Publishing Parcel Fabric Feature Class

Re: Problem Publishing Parcel Fabric Feature Class

Re: Problem Publishing Parcel Fabric Feature Class

Query Branch Versioned Parcels

Re: Migrating Parcel Fabric Data from File Geodatabase to SDE

MergeParcelsPythonAPI.zip

Parcel Fabric Active Record Automation

Meetup: Parcel Fabric Data Management

Re: Failed to paste. SDE or DBMS admin user cannot...

Re: MeetUp: Integrating Department of Revenue Dat...

Re: Editing Parcel Fabric in an ArcGIS Enterprise ...