Bug: When the Migrate Relationship Class tool is run on an attributed composite relationship class, the composite relationship is not maintained
【相关信息】
Article ID: 42781
Bug Id: NIM102762
Software:
ArcGIS for Desktop Advanced 10.2.1, 10.2.2, 10.3
ArcGIS for Desktop Standard 10.2.1, 10.2.2, 10.3
ArcGIS for Server 10.2.1, 10.2.2
Platforms: N/A
【BUG描述】
The Migrate Relationship Class geoprocessing tool used to migrate Object ID-based relationships to Global ID-based relationships corrupts table-based relationships. The types of relationship classes affected include attributed relationship classes as well as many-to-many relationship classes.
The result of this migration causes the relationship class to no longer function and the features in the relationship class no longer honor the relationship behavior. The workaround below provides a way to restore the original ObjectID-based relationship class prior to running the migration tool.
【BUG原因】
The Migrate Relationship Class tool corrupts table-based relationships (attributed and many-to-many) by populating the destination foreign key with values from the origin table instead of the destination table.
Article ID: 42781
Bug Id: NIM102762
Software:
ArcGIS for Desktop Advanced 10.2.1, 10.2.2, 10.3
ArcGIS for Desktop Standard 10.2.1, 10.2.2, 10.3
ArcGIS for Server 10.2.1, 10.2.2
Platforms: N/A
【BUG描述】
The Migrate Relationship Class geoprocessing tool used to migrate Object ID-based relationships to Global ID-based relationships corrupts table-based relationships. The types of relationship classes affected include attributed relationship classes as well as many-to-many relationship classes.
The result of this migration causes the relationship class to no longer function and the features in the relationship class no longer honor the relationship behavior. The workaround below provides a way to restore the original ObjectID-based relationship class prior to running the migration tool.
【BUG原因】
The Migrate Relationship Class tool corrupts table-based relationships (attributed and many-to-many) by populating the destination foreign key with values from the origin table instead of the destination table.
1 个回复
易智瑞技术支持
赞同来自:
The workaround for this issue is to re-create the original relationship class, providing that the original relationship keys are known.
1. Export the attributed relationship class table as a geodatabase table. a) Add the attributed relationship class to the map. b) Right-click the standalone table in the table of contents, and click Data > Export.
2. Use the 'Table To Relationship Class' geoprocessing tool to re-create the original relationship.(these are usually the last two fields in the list and have '_GlobalID' appended to the origin and destination feature class names).
3. Click OK to run the tool. Verify that the new relationship class table was correctly populated.
4. The corrupted relationship class can be deleted if necessary.
【创建及修改时间】
Created: 6/20/2014
Last Modified: 7/2/2014
【原文链接】
http://support.esri.com/en/kno ... 42781
要回复问题请先登录或注册