Latest Contributions by CherylTrine

I have an SQL 2016 geodatabase that has been registered to our Portal (10.9.1) on a Federated Server site for years.  Until now, we have not done editing through the portal using a feature service (I've been editing through Pro directly on Default).  It's now time to change that.  We will be moving to the utility network so I need to become familiar with branch versioning. In order to get this working for branch versioning, I had to add a new data store to the portal, although the default database was already registered to the portal.  Was this because when it was originally registered it was set to traditional? I created a branch versioned feature service with version management checked.  I then brought the feature service into ArcGIS Pro, created a named version and switched to that.  I could update and save attributes, but when I click on the map to create a new feature, the Create Feature tool pops up this error message: When I check the ArcGIS Server Manager logs, it shows: Decided to try editing in a web map from Portal.  I could update attributes in Default (I haven't figured out how to create a version for use in a web map, yet. One step at a time 🙂 ), but when I tried to  save a new feature, the following would pop up (no more helpful than those 99999 error codes): The Server Manager logs showed the following: Where does the problem lie?   Cheryl   ... View more

We have an enterprise SQL database and ArcGIS Server and Portal 10.9.1.  Up until now, we haven't worried about versioning because most of the time there has been a single editor meticulous about the quality of edits.  But things are changing, and we will be having other people edit through feature services.  Because their edits need to be vetted before they are committed to the database, I need to set up some form of versioning.  I am somewhat familiar with traditional versioning, having played around with it to learn what it was about.  However, I believe that Branched Versioning would be the preferred way to go in my scenario. I tried to register a dataset as Branch versioned, but immediately ran into problems because our editor tracking has been using database time, and it appears that Branch Versioning requires UTC.  Database time is preferable in our case because all of our work is done in one time zone, and it is what our workers would understand.  Is there a way around this UTC requirement, or is there some way to make it so that the users would see database time?  Or do I need to go back through all my datasets that would use branch versioning, disable editor tracking and convert their date fields to UTC so that timing is at least consistent withing the dataset? Thanks for any advice. Cheryl ... View more

I have ArcGIS Pro 2.9.6 on my machine and went to install untools.  The latest version that I can see is untools 2.9.5.1.  Is there a untools 2.9.6, or will the 2.9.5.1 work on ArcGIS Pro 2.9.6, or do I need to downgrade ArcGIS Pro 2.9.5? ... View more