Hello,
We have a feature class within an enterprise geodatabase (using SQL Server). This feature class is created from a table in the enterprise geodatabase that is routinely updated in SQL Server simply by dropping the table and inserting into a new one.
I have feature-linked annotation linked to that feature class. The feature class and its linked annotation are served in a map service.
Our method of updating this feature class based on the updates from the table has been to create an XY event from the table, copy the features, and overwrite the existing feature class. This produces a new, updated feature class exactly the way we'd like.
However, this seems to break the link to the annotation feature class. When the feature class is overwritten, new features appear without annotation labels, and old annotation label artifacts remain when the features they were linked to are deleted.
Does anyone have any experience with this? Is there a better way to drop and create new feature classes and maintain that annotation link? This is a fast and easy way to update my table/feature class and would like to stick with it, but the feature-linked annotation does not seem to work with it.
We have a feature class within an enterprise geodatabase (using SQL Server). This feature class is created from a table in the enterprise geodatabase that is routinely updated in SQL Server simply by dropping the table and inserting into a new one.
I have feature-linked annotation linked to that feature class. The feature class and its linked annotation are served in a map service.
Our method of updating this feature class based on the updates from the table has been to create an XY event from the table, copy the features, and overwrite the existing feature class. This produces a new, updated feature class exactly the way we'd like.
However, this seems to break the link to the annotation feature class. When the feature class is overwritten, new features appear without annotation labels, and old annotation label artifacts remain when the features they were linked to are deleted.
Does anyone have any experience with this? Is there a better way to drop and create new feature classes and maintain that annotation link? This is a fast and easy way to update my table/feature class and would like to stick with it, but the feature-linked annotation does not seem to work with it.