Why some items do not have an OOTB version?

[PaulaaO]

Hi,

I am currently reverting some customisations back to OOTB, however I came across on a few occasions on dictionary entries which are OOTB, but in the Versions related list there are displayed only the versions related to an update set; I am not able to see at all any history, OOTB versions as I do on most occasions.

Do you happen to know why is this behaviour? In most cases, the item is similar with OOTB (I am cross checking with my PDI), so I am a bit confused why in the Version related list I see listed an update set as it would have been a customisation.

Any advice would be much appreciated.

Thank you,

Paula

[PaulaaO · Accepted solution]

In case anyone else has come across this, I managed to raise it with ServiceNow directly and received the following response:

------

Reason: This is expected behaviour found under PRB1345155
Issue: When reviewing skipped changed you are unable to revert to OOB version.
Most Probable Cause: The records are created from a different type of file that isn't the usual XML file therefore it shows as not having an OOB version.
Solution Proposed: The reason there are no out of box records is that some records at a point during an upgrade may have moved to a different type of file update/upgrade as per PRB1345155. This is expected behaviour even if it may not be ideal.
If you want to have an OOB version for the records included, then you would need to compare with a personal development instance that has OOB setup.
Once you have compared and made exactly the same as the OOB version via update sets, then you can tick the replace on upgrade flag on the update and it should stop showing as skipped record