Updating a content version
Caution:
As
stated before, if you have made customizations to pages or components in your
existing content, you should first make this update in a test environment. You must
ensure that the customizations work with the new content in a test portal, before
activating the content in a production portal. Also see Comparing content versions for an update.
Also, the content version update may prompt you to update schema, which is a non-reversible operation. Before updating the content version, make sure you have a backup for the database associated with your LocalDataStore data source. If any problems occur, you can use the backup to restore the database.