GlobalID with 0's in delta Tables

[vijaybadugu]

When someone edits/create a feature in actual Feature class which was enabled with Version (traditional) options, the global Id's in delta tables are with 0's as shown in figure. How to get red of those? is there any configurations required to avoid this ? triggers are enabled on delta tables 

[MarceloMarques]

@vijaybadugu I saved my edits, and I checked the Adds Table of the Featureclass and the Global ID was populated correctly.

| Pro 3.3.0 | SQL Server 2019 CU 25 | ArcSDE Repo 11.3.0.3.3 |

If you continue to experience an issue, then open a ticket with Esri Support and provide a copy of your ArcSDE Geodatabase for support to try to reproduce.

[vijaybadugu]

I have just gone through the parent feature class which has 000-000 in global id and it has unique index on it . How can I update those records with new global ids ? Will that cause any issues on existing features in main feature class and delta tables ? 

[vijaybadugu]

We are getting this error while editing/creating feature with globalids as 00000000 . we are updating one of the attributes Acres through trigger on delta tables (A Table). do we need to update global id too ? 

[MarceloMarques]

You will run into all sorts of issues if you try to change behavior on traditional version tables, base table and adds table, by using custom database triggers, instead we use the multi version view if we need to manipulate the data via SQL, otherwise you will need to use ArcGIS Pro Attribute Rules to prepopulate values, some fields when using ArcGIS Pro automatically trigger the proper geodatabase behavior, like objectid, and globalids. If you continue to have issues, please open a ticket with esri tech support for further assistance.

An overview of editing versioned data using SQL—ArcMap | Documentation (arcgis.com)