Skip to main content

I have two enterprise geodatabases, each with an annotation feature class (annotation version 2.x) that I need to keep synchronized. Edits are made in the feature class in the source geodatabase, and (ideally) updated nightly to the feature class in the target geodatabase, using an automated FME workbench on FME server. The annotation feature class in the target geodatabase should have all of its features truncated and replaced by the annotation features in the source geodatabase feature class. This works great for a number of other feature classes (polygon, points, etc.), and it works fine with older versions of the annotation (Desktop version), but not for this annotation version.

 

I'm testing this out locally, using ArcGIS Pro 3.0 and FME 2022.0.0.2 (Build 22343), and regardless of how I set up my workbench, I'm not able to read and write the annotation features between these two data sources.

 

Currently, I'm getting the following error from FME Workbench:

 

"An error occurred while attempting to set the 'LinkedFeatureID' property on the 'IMEAnnotationFeature' interface for the pro annotation feature class 'test_annotation_fc'. The error number from ArcObjects is: '-2147467259'. The error message from ArcObjects is: {}"

 

Is there just some incompatibility between my version of FME Workbench and newer versions of the Annotation Feature class? FWIW, this annotation dataset was upgraded from the Desktop annotation version to the Pro 2.x version using the "Upgrade Dataset" geoprocessing tool in ArcGIS Pro.

The annotation feature class in question does not use linked features, so I'm not sure what's causing this error. Any ideas?

 

Same problem here :(

Have you found any solution to this problem?

Thanks in advance.


Hi @jesselangdon​ and @ostoja​,

Apologies for the late response on this. Would either of you be able to share your workspace with us? One of our developers tried to reproduce the issue but was unable to, so if we can take a look at one of your workspaces that might provide us with some hints. If possible, please share your workspace as a template by running it with Feature Caching enabled, then going to File > Save as Template. You can also share your workspace with us through our FTP; please give us a headsup if you do so. Let me know if there are any questions!


Hi @jesselangdon​ and @ostoja​,

Apologies for the late response on this. Would either of you be able to share your workspace with us? One of our developers tried to reproduce the issue but was unable to, so if we can take a look at one of your workspaces that might provide us with some hints. If possible, please share your workspace as a template by running it with Feature Caching enabled, then going to File > Save as Template. You can also share your workspace with us through our FTP; please give us a headsup if you do so. Let me know if there are any questions!

Hi @saraatsafe​ ,

sorry for not reporting it already.

My issue was connected to the bug in the workbench which resulted in having same GlobalID in the annotation feature as well in the GlobalID of the linked feature. As soon as I generated new GUID for GlobalID of the annotation feature, I was able to write into the Annotation FCL.


Hi @jesselangdon​ and @ostoja​,

Apologies for the late response on this. Would either of you be able to share your workspace with us? One of our developers tried to reproduce the issue but was unable to, so if we can take a look at one of your workspaces that might provide us with some hints. If possible, please share your workspace as a template by running it with Feature Caching enabled, then going to File > Save as Template. You can also share your workspace with us through our FTP; please give us a headsup if you do so. Let me know if there are any questions!

Thanks @saraatsafe​!

 

I've uploaded the template and last log file (which includes the error messages) to the FTP site as a zip file (Workspace_Anno_20230802.zip).

 

FYI, we currently are using the workaround of embedding a Python script in the workspace which deletes all anno features and copies from the source.


Thanks @saraatsafe​!

 

I've uploaded the template and last log file (which includes the error messages) to the FTP site as a zip file (Workspace_Anno_20230802.zip).

 

FYI, we currently are using the workaround of embedding a Python script in the workspace which deletes all anno features and copies from the source.

Hi @jesselangdon​, since you're reading in from an SDE it's tricky for us to test properly as we don't have a way to connect to it. However, in your log file there is an error on line 143: `geodb_linked_feature_id' has value `12569192'. Would you be able to try using an AttributeRemover to remove the geodb_linked_feature_id format attribute and see if this changes anything?


Reply