Latest Contributions by JonathanFarmer_oldaccount

Hi Thomas, Thanks for the detailed information on your plans and concerns. I'm going to get with some folks here internally and have a chat regarding this. I personally haven't gone down this road of geoprocessing history in the geodatabase with ArcGIS Pro as the sole client so I'm sure we'll need to do some testing and work to see what works and what doesn't. I should note though that we'll be supporting ArcGIS Desktop for a good long while. We have 5 year support cycles for the software, the latest release of 10.6 being supported until December 2023. There are still more versions of ArcGIS Desktop yet to be released as well so it isn't going away any time soon. More information on product life cycle below. Esri Support 10.6   Jonathan ... View more

Hi Thomas, How To: Delete geoprocessing history from a geodatabase  is still the go to for removing geoprocessing history from an enterprise geodatabase. This is the method we recommend to our users in Support Services. Moving forward, of course, we'll have to evaluate things like this. In Support, we've found that a lot of our users will have ArcGIS Desktop and ArcGIS Pro installed so it usually isn't an issue. In your case, it sounds like ArcGIS Pro is the only software in the production environment.  I'm wondering if the quick and easy way to get the GP history cleaned up is to run this script from a Dev environment or other environment that has ArcGIS Desktop installed? I should also note that deleting the geoprocessing history from the Catalog pane in ArcGIS Pro will only remove that history from the Project itself, not the geodatabase. Jonathan ... View more

Hi Jordan, Sorry, I wish I had a better answer here. However, I would suggest that you log this on the Ideas site if it is pretty important to you guys. I did a quick search and didn't find an existing idea. Those are reviewed by staff here so it may be worth the time to write up. https://community.esri.com/community/arcgis-ideas  ... View more

Hi Jordan, I see this is posted in the Enterprise section but this looks to be more of a Desktop editing workflow, at least the reconcile and post part. But let me know if I am off on any of my assumptions here. It sounds like you are working with one feature class, called say GPS. That feature class has a child version of Default called GIS. The feature class has been published (to Server? Portal?) and the published Feature Layer is being used in an app like Collector to add new data and edit data in the field. After they are done editing, they sync which brings down the changes to the underlying geodatabase and you are looking to perform the rec and post operation in Desktop correct? But you'd only like to rec and post a subset of the data? Like maybe OID's number 1-5?  If my assumptions are correct, there is not a way to do this currently. When you reconcile and post you are working with all of the data in the given feature class. The objective being to first pull down any updates from the parent version (reconcile), find and then resolve any conflicts, and then push up changes from the child version (post). But it is done on the entire feature class. Now, there may be some workflows you could use to get around this but it depends on a few things. For example, if you know that on a given day the workers in the field are going to be working on jobs A, B, and C then you could create child versions off of Default for those jobs. Then you could decide to only rec and post child version A and not the others. Or you could potentially split editing out into separate feature classes (and separate feature layers) to keep things separate? Just some thoughts.  Hope that helps! Jonathan ... View more

Hi Alicia, I'm going to let someone else jump in regarding your question on grouping categories together for symbology in AGOL. I'm not aware of a way to do this but someone else may. However, to your question on defining what is categorized as "Other", to my knowledge there is not a way to do this. The "Other" category is reserved for rows in the chosen column that do not have an entry. For example, if I choose to symbolize based on a column called "Pipe Type" and my 2 choices are "Water" and "Gas" then I should see 3 labels on my map in AGOL, "Water" "Gas" and "Other" where "Other" are the rows that do not have an entry in them (null values). Hope that makes sense. You can choose to hide features in the "Other" category though so they do not display on the map. Jonathan ... View more

Adrian, OK, that makes sense and sorry for the confusion. I'm running the latest 2.2 Beta on my physical box. Just tested with 2.1.3 on a VM and see the same behavior you do. So something to look forward to once 2.2 comes out! ... View more

Adrian, That's the right place. Do you just get the single pane GP tool when you create a new FC that way? If so, what version of Pro are you on? ... View more

Adrian, It depends on how you access the Create Feature Class tool. If you go to the Analysis tab - Tools - Create Feature Class. This will open the GP tool and the pane you saw. If, however, you right click on your geodatabase connection and go to New - Feature Class. You'll be walked through the 6 different pages in the pane to fill in the information rather than seeing it displayed in one GP tool. In this case, you would see the Fields option. And you are right, you'll need to recreate domains. Jonathan ... View more

Hey Adrian, We don't offer a way to import a schema from another feature class into an already existing one. You'd have to do it manually (or maybe the join option you mentioned). But I personally would just create a new one and import myself. Jonathan ... View more

Hi Scott, It may be hard to answer this question without a little more background information on what your end goal is here. Subtypes allow you to categorize features within a feature class that share the same attributes. For a given subtype, you could have either a range or coded value domain associated with it. For example, I could have a subtype of my Water Lines feature class called Copper. For a copper line, I could have a range domain that specifies the pressure allowed in that line, say 20-30 PSI or something. You get the idea. In this case, it depends on how you want people to work with this data? Subtypes and domains are great for workflows that involve heavy editing by many editors in order to cut down on data entry errors. Is that something that will happen in your case? Given the screen shot you attached, I could see something like a Facilities feature class with a field called Facility Contact. Facility Contact would be the subtype and maybe a coded value domain is put in place listing out the 5 types of facility contacts. You'd have to play around with it to see what works best. More information on subtypes and domains here: Introduction to subtypes—Geodatabases | ArcGIS Desktop  Hope this helps and let me know if you have any questions for me. Jonathan ... View more

Hi, Kory got with me on this post and I've been working to see if I could reproduce the behavior on my end based on the steps you mentioned. So far, I don't see this same error in either ArcGIS Pro 2.1.3 or 2.2 Beta.  These are the steps I took, can you let me know if I am missing something here? Created a new 10.6 Enterprise geodatabase on an Oracle 12.1.0.2 instance (SDE schema, using the Create Enterprise Geodatabase tool in Pro) Connected in ArcGIS Pro 2.1.3 as sys and ran the Create Database User tool to create a new UN owner user Made a connection in Pro as this new user I worked with the sample data for my test so I took the Naperville Electric feature dataset that includes all the needed information and worked with that. More information on that data is here: Get started with the Electric Distribution Utility Network Configuration—Get Started | ArcGIS for Electric  I ran the Create Utility Network tool using this Naperville data which created a new UN I then ran the Disable Network Topology tool as that is required before running Add Domain Network I then ran Add Domain Network which ran successfully I then right clicked on Structure Boundary in the Catalog pane and went to Design and then Subtypes I added a new subtype to ASSETGROUP I then clicked in the ASSETTYPE field and was able to choose a domain and click save with no issues It looks like we may need to get a support case created to further troubleshoot this issue. I can get a case created for you so that we can work together on this if you like? Just let me know and I'll do that. Jonathan ... View more

Hi Ernesto, I wanted to add on to George's comment, which is 100% correct, and re-emphasize that your IT staff should not delete anything from the database that was created when you enabled the geodatabase functionality in ArcGIS. Esri has put in place all of those tables, objects, and stored procedures to allow our clients (ArcGIS Pro, ArcMap) to work with the DBMS and provide all of the geodatabase functionality that is needed. Things like versioning, geodatabase replication, topology, networks, etc. For some more information on what a geodatabase is and how it is structured, see the links below:  What is a geodatabase?—ArcGIS Help | ArcGIS Desktop  The architecture of a geodatabase—ArcGIS Help | ArcGIS Desktop  But I would say the best message you can pass along to your IT staff as to why they should not delete these things they deem not needed is that we have only tested and certified a geodatabase to work with all of these tables, objects, and stored procedures in place and working together. If any one of them is removed, there is a chance that you may corrupt the geodatabase and lose data. If that happened and you didn't have a database backup handy, that could potentially be a lot of time and effort lost. Esri Support would not be able to help you get that data back either. Hope that helps. Let me know if you have any questions. Jonathan ... View more

Hi Miranda, I just happened upon your question here and wanted to address it. Deleting all versions in the geodatabase in relation to a Compress workflow is one of the ways that you can achieve a full compress. A full compress is when the StateID value for the Default version is at 0 meaning that all of the data for that particular feature is in the base table and nothing resides in the delta tables. For more information on achieving a full compress, see below: Fully Compress a Geodatabase: Geodatabase compression—Help | ArcGIS Desktop  It should be noted that this is not the only way to achieve a full compress. A user could reconcile and post all versions to the Default version and then re-reconcile all versions to Default again without posting. This gets around the need to delete the versions. I should also note that it isn't necessary to achieve a full compress during a standard compress operation, in fact, many of our users never do. But if you ever needed to unregister a feature class as versioned (as an example), you'd want to do this. Hope that helps! Jonathan ... View more