Assigning field values to DepthsA

[FeliciaNurindrawati]

Hello, I'm having trouble with the setting up the maritime geodatabase for the creation of S-57. This is something that I noticed after updating to ArcGIS 3.4, and I didn't bump into this error before that. 

I had a script that automatically sets the PLTS_COMP_SCALE to a user-defined value for Nautical/DepthsA. This script uses the CalculateField to assign this value. However, after updating to ArcGIS 3.4, it appears that using CalculateField through the script corrupts the features, as exemplified in the following screenshot. It worked when I use CalculateField outside the script (separately as a geoprocessing tool). Why would  DepthsA get corrupted when I use a script to change the field values?

[Tobias-Venable]

Hello Felicia,

Could you confirm you also see the invalid GlobalID value in the table view as well?

Do you have any customizations on this Maritime schema? Would you be able to provide the script you're running to see if we can reproduce this behavior?

Thank you!

[FeliciaNurindrawati]

Hi Tobias! 

Unfortunately I cannot confirm the GlobalID value in the table - it returns an error when I try to open the table. Only when I click on the layer that I can see that the GlobalID is corrupted. I also do not have any custom Maritime schema.

The script that I used automatically appends contours, soundings, and other features to the geodatabase, but the GlobalID error was observed to happen after the CalculateField portion. We have since found a work around by separating the CalculateField portion to a separate script from the append script, so I would consider this solved. Still puzzled why the error happened though.