ArcPro 2.4.2: Adding a version to the table of content gets the default version identical to it,

[JamalNUMAN]

ArcPro 2.4.2: Adding a version to the table of content gets the default version identical to it,

I couldn’t figure out why adding a version to the table of content gets the default version identical to it! Is this a bug?

With the same data, ArcMap is working as expected. Adding the version doesn’t affect the default to move to get identical to the version!

[MichaelVolz]

What were the steps you followed to get this phenomenon to occur?

Did you use SDE connection files already built in ArcMap or did you create these SDE connections from scratch in Pro?

What type of relational database are you using as well as type of database client?

[JamalNUMAN]

Thanks Michael

-An SQL Server database is created (named as Q1)

-A direct connection is made on Q1 by sa in ArcPro

-The Q1 is enabled as set as “protected”

-A feature class (L1) is created in Q1

-L1 is set as versioned

-6 points are created on L1

-A user (u1) is added to this Q1

-u1 is granted a full access to L1

-u1 creates a version from Q1

-u1 and sa edit the same feature

-This edited feature is expected to be detected as a conflict when reconciling