Notifications

106 views

Symptoms


Custom table was not created properly when committed via update set.

 

Release


All

 

Cause


  • Manually modifying <system_xml_records> and moving them between update sets is a consistent source of errors. 
  • The table was originally created in another update set and then the update records were manually moved to the other update set.

Resolution


Delete and re-capture the table creation. If the creation of a table or column is accidentally captured in the wrong update set, delete it and recreate it in the correct update set instead of attempting to move it manually.

 

 

Article Information

Last Updated:2018-05-18 13:50:02
Published:2018-05-18