Latest Contributions by RyanUthoff

The ObjectID field is typically controlled by Esri and the end user typically doesn't have any control over it, especially in an ArcGIS Online context. You do have some limited control over it when exporting data to FGDB's (like being able to maintain the ObjectID when exporting), and you might be able to specify the ObjectID directly in SQL (which typically isn't recommended). But that doesn't really help with AGOL. That is all controlled by Esri and I'm not aware of any way to preserve the ObjectID when uploading records to AGOL. I'm just taking a shot in the dark here, but you might be able to export your dataset to a FGDB (use the Copy tool which preserves ObjectID). Then upload that FGDB to AGOL and publish a feature service from it. It's possible it might maintain the ObjectID using that workflow, but it's not something I've personally tried. Because it seems like you're trying to add records to an already existing feature layer, which you probably won't be able to manage the ObjectIDs. But if you create a new feature layer from your FGDB, it's possible AGOL will preserve the ObjectIDs depending on how AGOL is creating that feature layer. Edit: I just tested the workflow and I have confirmed that it does maintain the ObjectID (in my very limited test). ... View more

There is no going back once you run the Enable Enterprise Geodatabase tool on a DB. Your best bet is to restore your DB from a backup from before you ran the tool. You can try deleting all the Esri system tables, stored procedures, etc. in SSMS, but the only for-sure way that you'll be able to eliminate anything Esri related in the DB is to restore from a backup since before you ran the tool. ... View more

After changing the column length, you will need to restart (or potentially republish) your feature service so the field length is updated there. But otherwise, yes, changing the column length in the EGDB will be reflected in everything down the line. ... View more

Do you have snapshots of your machine? Or at least a WebGISDR backup? That might be your quickest solution at this point to get you back up and running. Alternatively, you can try and do a repair of the Portal installation (go to Control Panel and click "change", and then the dialog box will give you an option to repair it.). I was installing a Portal patch and during the installation, the machine became unresponsive and I had to do a restart which corrupted Portal. Doing a repair fixed it and I did not lose any of my content. But I can't guarantee it'll maintain any custom Portal configuration you might have. ... View more

If the tables already exist before enabling the EGDB, then yes, you will need to register each table in the DB. ... View more

I would like a little clarity from Esri regarding this statement: "The reason behind this is that the coordinate system plays a crucial role in setting important parameters such as the spatial domain (range of coordinates), XY/Z/M tolerance, and resolution values. If a coordinate system is left undefined initially and then set later, those spatial properties might not align properly — which can lead to data integrity problems." Wouldn't you expect to see more data integrity issues when using the Define Projection tool on a known coordinate system as opposed to an undefined coordinate system with no records in it? Edit: One last thing. ArcGIS Pro error 000146 states that the "Define Projection tool works with a dataset that does not have any coordinate system." But that directly conflicts with Esri's response to you, stating that "Define Projection tool cannot be applied to a feature class with an Unknown Coordinate System." Either there is a misunderstanding somewhere, or the documentation needs to be updated to reflect that the Define Projection tool cannot be used on unknown coordinate systems. ... View more

I'm just......confused by this "issue" along with Esri's response. Per Esri's documentation, it literally says the Define Projection tool is "intended for datasets that have an unknown or incorrect coordinate system defined." But you're saying that Esri said that the tool is not intended for datasets with an unknown coordinate system. That doesn't make sense, because isn't that the point of the tool? I'm not sure if I'm missing something, but that just doesn't make sense to me. I'm not sure if you've already closed your case with Esri support, but I'd push back and state that their documentation explicitly states that what you are wanting to do is possible per their documentation. ... View more

Getting the terminology correct here is pretty important. When you say "postgres server", I am assuming you are referring to the ArcGIS Data Store from how you are describing it. Under the hood, the ArcGIS Data Store is a postgres DB. However, this is not a DB you should ever directly interact with.  If you are in fact referring to the ArcGIS Data Store, you should NOT upgrade the version of postgres. Any upgrades should ONLY be done through ArcGIS Data Store upgrades (like going from 11.4 to 11.5). Sometimes the ArcGIS Data Store upgrade will also upgrade the version of postgres, but you should never independently upgrade postgres. To answer your question about how Portal uses the postgres DB, it's typically only used for hosted feature services. It makes sense that when you shut it off, that only hosted feature services stop working.  ... View more

If you have data elsewhere that you would like to add to the underlying feature service that drives the S123 form, you always bring in the S123 feature service into ArcGIS Pro and just append your existing data into the S123 feature service. ... View more

If editing is disabled on the layer in the map, you can enable editing in the layer properties. Open the properties of the layer which and enable editing. RyanUthoff_1-1748630683121.png   ... View more

You can click the Edit button on the right side of the screen and that will allow you to edit records with editing enabled. RyanUthoff_0-1748630253202.png   ... View more

We encounter this exact same "problem." We have a few hundred surveys, all of which have photos in them which consume a lot of storage space on the server. And unfortunately, just "deleting" the photos through Esri isn't good enough. Under the hood, the ArcGIS Data Store is just a PostgreSQL DB. And for surveys (or any hosted feature services with sync enabled), Esri typically treats them as a "versioned" dataset, where you have your base tables along with the associated versioned tables. When interacting with the data through Esri, it's always using the versioned view. So for example, if you're viewing the data in ArcGIS Pro or in Portal, you're looking at the versioned view of the dataset. And any modifications you make, including deleting the data, get reflected in the view, but not necessarily the underlying base table. If I delete a record in Pro, that will be reflected in the view, but not the underlying base table. This is where it becomes a problem, because it gives you the impression that the data is deleted, but it actually isn't. Unfortunately, this is where it becomes difficult to fix the problem because Esri doesn't really have any out of the box tools to deal with this. Several years ago at the UC, someone from Esri told me that you can disable sync and then re-enable sync capabilities of the hosted feature service, and that would get the changes you made in Pro/Portal reflected in the underlying base tables and that would truly "delete" all the records. While I believe that is technically correct, it also corrupted the hosted feature service for us (I think because we had a huge feature service and it timed out or something). So we don't use that method. The alternative method is connecting directly to the Data Store DB directly through PGAdmin. From here, you can delete the records in the base table. However, deleting the records from the table does not actually decrease the table size or give the space back to the OS. The final step you have to do is run a vacuum full command on that table in PG Admin. What that does is actually free the space back up to the OS, and will also result in smaller Data Store backup sizes. Edit: Just to add, I created an ArcGIS Idea several years ago about this. ... View more

Esri's system log parser should be able to do that (and much more). https://community.esri.com/t5/implementing-arcgis-blog/arcgis-enterprise-analysis-with-system-log-parser/ba-p/1189005   ... View more