2

We are doing Sitecore upgrade from 9.2 to 10.2. We are using XP topology hosted in On Premises. In 10.x. Sitecore introduced IAR (Items As Resource) to manage Sitecore default items such as templates, renderings, layout etc., While doing clean up DB using Sitecore Update App, we found that there 35+ items are registered in log file which we have to do clean up. So we are deleting those items from DB and apply the customization manually. I have below questions:

  • Is this clean up activity mandatory? What would be impact if we are not doing?
  • Is there any quicker solution available for applying customization for those default items?

1 Answer 1

1

We recently did a similar upgrade and had the same questions (as the log files identified close to 200 modified items).

The reason it is important is to ensure that your Sitecore solution is using the most up to date versions of those items.

The log files give an indication of what field on the item has been altered, so based on that information you could decide its not worth making the change. However, you risk missing some important change between old and new. The safest bet is to delete the item (and corresponding fields values) from the SQL DB and then reapplying through Sitecore.

One thing I would stress though, is that it is very important that you apply these changes to all publishing targets after you do the master DB (as mentioned in the upgrade docs).

Failure to do this can lead to content being deleted on publishing targets.

4
  • Thanks Dean..Agreed..instead of applying customization manually, can we take package and install of those OOB items from other environment where upgrade is not yet done.
    – Thamizh
    Commented Jun 8, 2022 at 11:48
  • If you are taking a package from an environment that isnt yet upgraded, then you definitely should not be installing over the upgraded environment, as this would bring across possibly old versions of the items. Commented Jun 8, 2022 at 12:15
  • Unfortunately you need to follow the sitecore recommendations and apply the changes via sitecore backend manually after removing from the database. You could save time, by then packaging those changes (from upgraded environment) up and installing in later upgraded environments. Commented Jun 8, 2022 at 12:19
  • Yup..Thanks Dean..
    – Thamizh
    Commented Jun 8, 2022 at 12:36

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.