Unexpected Error. Cannot save or move object 'XXXXX' with id 'XXXX' and type 'DB Table'. Its dependent object with id 'XXX' and type 'Column' does not exist in the metadata.
CAUSE:This issue is caused by a physical table object left in the metadata even though its logical table has been removed from the project. This physical table object has references to multiple invalid columns which causes the error to be thrown.
ACTION:Contact Strategy Technical Support for further assistance. In order to track down the cause of the inconsistency, customers encountering this issue should make note of Schema-related changes, Object Migrations or error messages prior to experiencing the problem. Change Journaling, if it has been enabled, can help in preserving this information.
