When changing the value of the Shared or Unversioned property of a particular field, every item based on the modified template is updated and the corresponding field values are moved to the appropriate data table in the Sitecore database: SharedFields, UnversionedFields, or VersionedFields.
However, in situations when the field sharing properties on a template are changed as part of a package installation, related items may not be updated properly, and corresponding field values may be located in different Sitecore database tables.
In this case, an author may experience various issues when working with items.
For example, field values may not be changed as expected upon save operation, or the data may not be published in an expected manner.
If one the previously installed packages has already modified the field sharing properties, perform the following steps.
Notes:
Solution:
After performing these steps, all the field values should be stored in correct places and unexpected results of the package installation should be fixed.
To prevent this issue for future package installations, perform the following steps.
Note: The solution below applies only to SQL Server databases.
Solution:
<WizardForm Application="Tools/Installer/InstallationWizard" CodeBeside="Sitecore.Shell.Applications.Install.Dialogs.InstallPackage.InstallPackageForm,Sitecore.Client">with the following one:
<WizardForm Application="Tools/Installer/InstallationWizard" CodeBeside="Sitecore.Support.Shell.Applications.Install.Dialogs.InstallPackage.InstallPackageForm,Sitecore.Support.310642">
<setting name="FixFieldSharing.DatabasesToMaintain" value="master, web"/>In the value attribute, you can specify the names of the databases that should be checked after future package installations.