SpatialReference differs between ArcGIS Pro and ArcGIS Pro SDK

TorbjørnDalløkken2

I have a filegeodatabase containinig a dataset and some featureclasses. The dataset is originally created with the spatial reference ETRS 1989 UTM Zone 32N.

One of the features in the add-in is to change the spatial reference of this dataset based on some values from a list. The code runs the "Define Projection" tool and the dataset is being updated with the new spatial reference. ETRS 1989 UTM Zone 32N to ETRS 1989 UTRM Zone 33N (or 35N).

When I try to get the spatial reference of one of the featureclasses through ArcGIS Pro SDK:

await QueuedTask.Run(() => 
{
  using (Geodatabase geodatabase = new Geodatabase(new FileGeodatabaseConnectionPath(uri)))
using (FeatureClass featureClass = geodatabase.OpenDataset<FeatureClass>("JSRGrensepunkt"))
{
    var featureclassDefinition = featureClass.GetDefinition();
    var sr = featureclassDefinition.GetSpatialReference();
    /* more code ...*/
});

GetSpatialReference() returns the original spatial reference (32N) and not the current one (33N):

If I look at the same featureclass in ArcGIS Pro, I can see that the featureclass indeed is in 33N:

What might be wrong here?

danretired

correct, I omitted the case of incorrect coordinate system

Define Projection (Data Management)—ArcGIS Pro | Documentation

and the cases where it can't be used include (in Pro 3.5) are:

The tool does not support the following:

A feature class in an enterprise geodatabase
A feature class in a feature dataset
A feature dataset that contains a feature class

As well as several paragraphs clarifying other exemptions and suggests creating a new gdb under some circumstances.