Latest Contributions by MelissaJarman

‎07-21-2022

FYI - The duplicate idea was implemented.

‎07-18-2022

The Default version is the default for that specific versioning type for the entire geodatabase – eg: All branch versioned datasets for the entire enterprise geodatabase. Because different database users could own different branch versioned datasets in a geodatabase, keeping the access permission restricted as the geodatabase admin is best. We are interested in hearing additional use cases from our users based on business needs.

‎07-18-2022

Sorry for my delay in response. I am able to create a simple view of a spatial table and view this in ArcGIS Pro, so it may be something more specific to your workflow or data. If you haven't already I would suggest to contact our Support Services team to see if they can provide more assistance.

‎06-24-2022

For the spatial tables in Redshift, we do support spatial columns with geometry type. Geography is newly added for Redshift and has not been certified by our development team yet. Are you just using drag/drop to add to a new map? Are you using the actual table, or a view of the table? Does the table have a unique not null column?

‎05-23-2022

This is reserved for helpful resources for the 2022 user conference sessions on branch versioning: Core documentation – Branch version scenarios REST API – Version Management Service Blogs – To Branch or Not to Branch – An Introduction to branch versioning Branch Versioning: Setting the Stage Editing and Administration with Branch Versioning – It’s Showtime! Version administrator for branch versioned data New Manage Tab on Properties Page Sessions - UC 2022 branch versioning presentations Enterprise Geodatabase: Branch Versioning (Technical workshop) Enterprise Geodatabase: Demonstrating Branch Versioning Workflows (Demo theater) Documents included: Presentation slides in PDF for both sessions Summary questions and answers from both sessions

‎03-24-2022

If you are wanting to script this then getting a list and passing into the tools you mentioned is going to be your best bet. https://developers.arcgis.com/rest/services-reference/enterprise/delete.htm If you use the Versions view in Pro, you can select multiple versions at once using the SHIFT or CTRL keys and delete these. https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview/manage-branch-versions.htm

‎03-24-2022

Were you able to resolve this problem by process of elimination? More than likely the data in the feature dataset doesn't support this versioning option, or you already have some data in the feature dataset that is registered as versioned that does not use this option. Did you check the individual properties of all the classes in the feature dataset to make sure they are not already versioned and not using this option?

‎03-08-2022

Plans to add a new ArcGIS Pro option at the application level to set the default versioning type for new enterprise geodatabase connections that use the Database Connection dialog UI. This setting will not impact connections created using the Create Database Connection tool as there are already options in this tool to set the version type. As far as I know, the Stage Utility Network tool uses the Update Geodatabase Connection Properties To Branch for connections to ensure the correct versioning type is used. We are not wanting to 'lock down' the entire geodatabase to a specific versioning type because you can have mixed registrations types of data in a single geodatabase.

‎02-14-2022

Having the ability to set the default versioning type for new database connections would be a good enhancement to making database connections where you always wanted a specific type of versioning to be used.

‎02-09-2022

This is an area we have on our radar for adding a way to delete network attributes from a utility network. To properly track this request for other users that also have this same request, I would suggest you create a community idea for this or contact support services to assist in logging an enhancement request.

‎01-11-2022

Jimmy - I would recommend you contact support once you get a consistently reproducible case for any type of error that is preventing you from saving. You should be able to work in a user version and validate your edits. There are many conditions in play when performing edits in a user version and working with dirty area management with a UN. While you can get general pointers here, our support group would be able to take a closer look to give you guidance.

‎12-14-2021

Yes that is a proper workflow. I think the workflow you have outlined is good because you would want to validate your edits in your user version prior to reconcile/post to make sure you aren't violating any rules that would generate errors based on your edits. I think you just were not expecting the post to default to generate dirty areas again. Just know that edits brought over are going to generate dirty areas in default even if they are validated in the user version prior. This topic touches on this a bit as you have outlined in your workflow: https://pro.arcgis.com/en/pro-app/latest/help/data/utility-network/dirty-areas-in-a-utility-network.htm

‎12-03-2021

Sorry I don't have a specific solution to recommend. XML workspace documents do allow schema only option, so this is a reasonable workflow for you to attempt. To troubleshoot this I would try the process of elimination to isolate the culprit that is causing the import to fail. Perhaps exclude the views in your first pass and go from there to see if the cause can be determined.

‎11-24-2021

I hadn't thought about doing it that way with the Select By Attribute tool. It looks like this equivalency idea you linked is under consideration. I also found out that you can make a selection in the map view and then use the Attributes pane > Selection tab. When you initially open the Attributes pane it will give a warning about the violation of the attribute domain. From here you can further use the context menu to change the selection to ONLY include the invalid features. https://pro.arcgis.com/en/pro-app/latest/help/editing/edit-feature-attributes.htm#ESRI_SECTION1_8F13A8C397F349C9BF97D3DF2353E69F

‎11-22-2021

There are a lot of things that could be going on depending on the amount of data that is included in the XML workspace document from your EGDB. Let us know how many datasets and what types of datasets are included. Are you using any special datsets other than tables and standard feature classes? I noticed it looks like you're doing schema only, but have you tried other data transfer methods such as copy/paste since you are going to FGDB? Lastly, have you attempted this export and import to XML from the latest version of ArcGIS Pro?

Online Status	Offline
Date Last Visited	2 hours ago

My Ideas

Latest Contributions by MelissaJarman

Re: Rename SQL Server Geodatabase

Re: Branch Versioning Default Access Permission Changes - Status changed to: Closed

Re: Can not view spatial features from Amazon Redshift database ArcGIS Pro 2.9.3

Re: Can not view spatial features from Amazon Redshift database ArcGIS Pro 2.9.3

UC 2022: Branch Versioning (resources)

Re: Delete multiple branch versions at once?

Re: REGISTER AS VERSIONED = EDITS TO BASE (GREYED OUT)

Re: Turn on Branch Versioning by default when Staging a Utility Network - Status changed to: In Product Plan

Re: Turn on Branch Versioning by default when Staging a Utility Network - Status changed to: Under Consideration

Re: Delete Network Attributes

Re: Validate Network Topology Workflow

Re: Validate Network Topology Workflow

Re: XML Workspace document import duplicate error

Re: How can i find not members of the domain value

Re: XML Workspace document import duplicate error

Re: Attribute Rules - All fields must be visible?

Re: View Connection to a Lock

Getting to Know Esri Support: Stephanie W.

Re: Write to Snowflake database from Portal web ap...

Re: Version Management Service - Start Editing Ses...