Hello everyone,
I'm facing an issue when connecting my PostgreSQL database to ArcGIS Pro. I am using a user with superuser privileges, so I have full access to the database and its contents, including editing rights.
However, after I successfully add the database connection and drag layers into ArcGIS Pro, the layers appear as read-only views. I am unable to edit the features or create new ones using the "Create Features" tool.
I'm wondering why this happens. Given that I have superuser privileges, shouldn't I be able to edit the layers directly?
Has anyone faced this issue before? Any suggestions or workarounds would be greatly appreciated.
Thanks in advance!
Is the PostgreSQL DB an "Enterprise Geodatabase" (with SDE schema)?
If not, you cannot edit the data directly in a database (non-geo): https://pro.arcgis.com/en/pro-app/latest/help/data/databases/databases-and-arcgis.htm#ESRI_SECTION1_...
Hope this helps!
Hi George,
I used the second option — uploading the required layers to ArcGIS Portal, then adding them to ArcGIS Pro, as described in this link (https://esriaustraliatechblog.wordpress.com/2023/02/12/can-i-edit-data-in-a-database-not-enabled-as-...).
However, I ran into the following issue:
Message: Unable to complete operation.
Details: Rowbuffer creation failed. Underlying DBMS error [ERROR: Geometry has Z dimension but column does not]
The geometry type of the layer is MultiLineString, 4326.
Is there a solution for this?
I tried enabling the Z dimension, but then I encountered other errors like:
ERROR: Geometry type (LineString) does not match column type (MultiLineString)::SQLSTATE=22023
ERROR: Geometry has M dimension but column does not
I am not sure on that specific error message. Do you have a need to the Z value to be enabled?
If not, may want to recreate it without the Z value.
The image shows the error that appears to me
I would recommend contacting Technical Support on this. It may take more detailed troubleshooting than we can accomplish in this forum.
If you enable the database as a geodatabase and register that layer with the geodatabase, I wonder if the behavior is different.
Are the tables versioned? If they are, you would need to edit them in a version.