Latest Contributions by George_Thompson

What is the version of the geodatabase and RDBMS flavor / version being used? Have you updated the Enterprise Geodatabase to Pro 3.2? You could also run these 2 tools to see if there is any reported errors: https://pro.arcgis.com/en/pro-app/latest/tool-reference/data-management/diagnose-version-metadata.htm https://pro.arcgis.com/en/pro-app/latest/tool-reference/data-management/diagnose-version-tables.htm Do NOT run the repair without a full and verified backup. ... View more

If you are using the Pro 3.2 client for the upgrade, it may be due to version of the geodatabase. You will need to do an intermediate upgrade to 10.6.1 or newer first, then you can go to Pro 3.2. I did notice that you can use Pro 3.0.x as it will upgrade from 10.4.1. Pro 3.2 help:  https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/manage-sql-server/upgrade-geodatabase-sqlserver.htm You can upgrade directly from a 10.6.x, 10.7.x, 10.8.x, 10.9.x, or 11.x geodatabase if your database release is supported for the ArcGIS version to which you upgrade. If SQL Server is not at a release supported for the geodatabase version you upgrade from and the geodatabase version you upgrade to, you may have to upgrade the database and geodatabase multiple times before you can upgrade the geodatabase to the latest version. For each intermediate geodatabase upgrade, follow the upgrade instructions for that geodatabase version, and test the geodatabase as you move from version to version. ... View more

It still looks like the trace network is still owned by the SDE user. If that is the case, you need to copy over (or reload) the trace network in as the database user that you created. That DB user must have all the permissions to own data (https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/manage-oracle/privileges-oracle.htm).  ... View more

You must  load the trace network into another data owner for the tool to work: https://pro.arcgis.com/en/pro-app/latest/help/data/trace-network/create-a-trace-network.htm The input feature dataset must be from a database connection established as a database-authenticated user and owner of the input feature dataset. This user must have database privileges to create content and cannot be an OS-authenticated user, a database administrator, or the geodatabase administrator account. This database-authenticated user will become the database trace network owner on creation of the trace network. ... View more

This may be something that is best suited for your Esri Account manager. I am not sure that anyone in the Esri community can provide a valid response based on your contract. ... View more

For BUG-000150561, it is closed and a duplicate of another issue (BUG-000135099) which is showing as fixed in Pro 3.1; https://www.esri.com/content/dam/esrisites/en-us/media/products/arcgis-pro-issues-addressed/arcgis-pro-3-1-issues-addressed.pdf   ... View more

Not an easy way that I know of. One potential option would be to make a REST service from the Azure SQL, then consume that service in an Online Notebook and then you may be able to use ArcPy there. ... View more

@VanessaSimps can you post an error message? You may want to create a new thread for this. ... View more

Maybe use the calculate rule: https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview/calculation-attribute-rules.htm ... View more

I would start with a file geodatabase, unless they require a RDBMS to be used (like SQL Server / PostgreSQL / Oracle). Here is some doc to help you along: https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview/an-overview-of-creating-geodatabases.htm  You could then at least have all the geospatial data in a single location. I would agree this is a large task, especially if they do not have anything already, but can be done with lots of questions (as you are already doing). ... View more

Q1: Can you please confirm that the only way to create these classes is with a client? We can't do it with a standalone script via an API? Not even ArcGIS API for Python? Again not a developer or have extensive knowledge of all our API's (I am a Geodatabase person 🙂), but there may be a way with API for Python. Using ArcPy / Pro client is the easiest for setting up the layers   Q2: So what's the actual workflow here for the entire process of putting data into the EGDB? It seems rather convoluted. Also, is there a link to some documentation on this please. Which one is the "PythonAPI" you're referring to? Is that ArcPy or "ArcGIS API for Python" or something else? I'd prefer to use a RESTful API rather than the ArcGIS API for Python if there is one. Python API = ArcGIS API for Python, which is more the developer route (as I understand it) ArcPy = python package that is included with ArcGIS clients / software (see below for example of ArcPy) Loading feature classes: https://pro.arcgis.com/en/pro-app/latest/help/data/feature-classes/create-a-feature-class.htm  Using Python API for editing features: https://developers.arcgis.com/python/api-reference/arcgis.features.toc.html  As I understand it, you would need to publish a service then you could use the REST API for updating the data. If that is the preferred route. Then you could this: https://developers.arcgis.com/rest/services-reference/enterprise/get-started-with-the-services-directory.htm    Q3: That would be much easier, and my personal preference, but it looks like the project wants to go the EGDB route. If you project team wants to use the EGDB, then they should be able to create the feature classes or give you access to ArcPy and license to create what is needed. ... View more

Ah ok. In order to load data into the Enterprise Geodatabase (EGDB), you would need to create the feature classes via an ArcGIS client. Usually, people would do this via ArcGIS Pro or ArcPy. Once you have the feature class in the EGDB you could use the PythonAPI to update the data. There may be some limitations based on the licensing level of your client, but if you have Standard / Advanced you can do most things. Just an item to note: you can load data into the PostgreSQL database (using PG_Geometry / PostGIS) and ArcGIS clients can read that data. The ArcGIS clients would not be able to edit the data (https://pro.arcgis.com/en/pro-app/latest/help/data/databases/databases-and-arcgis.htm). This data would not be able to take advantage of the advanced functionality of the EGDB (domains / topology / relationship classes / etc. - https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview/fundamentals-of-the-geodatabase.htm)  Hope this helps! ... View more