KB4892: How to remove and re-add a Warehouse table in a Microstrategy 9.4.1 or 10.x project.

SYMPTOM:
Requirements may arise where a warehouse table needs to be removed from a project.\When trying to remove a warehouse table from a Strategy 9.4.1 or 10.x project, users should perform the following steps:

• Right-click on the table name under the schema objects/tables folder. Search the dependents.
• Double-click on the object name to open the attribute editor, for every attribute that appears in the search result.
• Modify the attribute forms to change the primary lookup table to another source table. Highlight another source table and click on 'set as lookup'. If a form does not have another source table, the form expression would have to be removed.
  

• Open the warehouse catalog editor, go to options, schema tab. Make sure the setting 'map schema objects to the new tables automatically' is checked.
  

• The table can now be removed from the project in the warehouse catalog editor.
  

• When trying to save and close, the Warehouse catalog prompts users with the dialog:
  'The following tables to be deleted still have dependent objects.'
  This is due to the Warehouse catalog searching on all objects that are connected to that table. The Search editor, on the other hand, only searches for objects that use the table as the primary lookup table.
   
  Select 'proceed with the changes.' Strategy Desktop removes the table as a source table for all attributes that use the table as a source table.
  

• Open the Warehouse catalog editor and move the table back to the right to add the table back to the project.
• Users may see the following dialog box when trying to save and close.
  

• Double-click on the item to resolve the conflict.
  

•  
  The conflict is present because the attribute 'Distribution Center' defined off the Country_Id column in the LU_DIST_CTR table. Country_Id is also present in the LU_Region table that is used to define the attribute 'Country'.
  

• Close the project before going back to the attribute and re-select the correct primary lookup table. Without this step, Strategy Desktop displays the attribute definition that is stored in the local memory. Once the project is closed and re-opened, the engine is also removed of the old definition, a task that can also be accomplished by update schema.
   
  NOTE: The attribute can be modified without closing the project. Remember to update the schema under the schema menu after the modification.