Sample code/error:
One or more columns were not found in table 'XXX'. Other objects use some of these columns. Removing these columns can leave the affected objects in inconsistent state.
The table structure will not be updated until no objects depend on these columns. Please modify the definition of the affected objects before continuing.
CAUSE:
In this particular scenario, the column as identified in the error exists as a duplicate, but its duplicate is a managed object so the custom test will not remove it. This was identified by checking the dependent object referenced in the error message and noticing the column used within the object was a managed column. Tracking this down the line, it was noticed that the DBTable object held the managed column in its collection rather than the column within System Objects/Columns as is typically seen. When updating table structure, it was complaining that it wasn't finding the managed column which was in the table because it was finding the correct column (within System Objects/Columns) during the update table structure. The database table referencing the managed column rather than the System Objects column is incorrect behavior and currently it is unclear how it came to be in that state.
ACTION:
Contact Strategy support for help in identifying the incorrect reference within the DBTable object and for corrective steps in fixing the table reference.
This issue has been logged as Scopus ID 679206 and 000024326
