Latest Contributions by MelissaJarman

‎01-13-2023

‎01-13-2023

Since you are using traditional versioning, you more than likely are not using archiving - so that Add Archive comment above won't work. This is something automatically enabled for branch versioning. It sounds like you are wanting something that is similar to the Version Changes command that opens the Differences view, but with the ability to specify a particular job for the thing to provide differences for. Let's see if other users would also benefit from this by who comments or Kudos this idea. Thanks! View traditional version changes

‎12-27-2022

Hi Veronica - I have a few questions to clarify this idea a bit further. What type of versioning are you using? Traditional or branch I am trying to determine if you are looking for something in ArcGIS Pro generally, or something in workflow manager specifically for each job. Have you tried to used the Add Archive button to view the archive class in the map and work with this using definition queries based on the archive fields? This is not an automatic display of the differences in a specific edit session, but you could view what was edited based on a specific GDB_FROM_DATE attribute value using a definition query on the archive class. Work with the archive class

‎11-01-2022

@DirtDogRoj - this sounds like it is the same as the following enhancement (equivalency from ArcMap). I would suggest you contact support and get linked to this. ENH-000139001 - Please Allow Pro to Select/Highlight the Associated Connection When User Selects 'View User' Under the Locks Tab in Geodatabase Administration

‎09-20-2022

The Change Version context menu and button in the Versioning tab on the ribbon are changing the version for all layers that share the same workspace. This is specific to the items in the map document being connected to the same workspace based on the database connection or feature service they were added from and the version they are currently referencing. NOTE: It looks like the Change Version tool was enhanced in 2.8 (Data Management gp history) to add the Include participating classes of controller dataset parameter. You mentioned: can you expand a bit more on this ? Unfortunately, having multiple layers with different versions can cause problems. Also looping through ALL the layers in the active map can also be problematic.

‎08-03-2022

@RadhakrishnanNeelakantan - We do not yet have a technical whitepaper for branch versioning. Most of our content has been in the form of blogs and core reference documentation. Please share what type of information you are looking for specifically in the whitepaper.

‎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.

Online Status	Offline
Date Last Visited	2 weeks ago

My Ideas

Latest Contributions by MelissaJarman

Re: Report generated after edit session - shows what was changed from last saved version - Status changed to: Open

Re: Report generated after edit session - shows what was changed from last saved version

Re: Report generated after edit session - shows what was changed from last saved version - Status changed to: Needs Clarification

Re: View Connection to a Lock

Re: Add an option to the Change Version to change all layers not just a single or group of layers.

Re: UC 2022: Branch Versioning (resources)

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

View properties of database sequences

Re: branch versioning historical moment

UC 2022: Branch Versioning (resources)

Re: REGISTER AS VERSIONED = EDITS TO BASE (GREYED ...

Re: Feature services vs Direct database connection...