We have moved to GitHub Issues
Created by Thomas Morris 06 Jul 2016, 15:25:36 Updated by Thomas Morris 20 Jul 2016, 09:17:44
Just raising this one for reference whilst I remember. I have overcome my issue, but it would be good if this could be looked at for a future release if anyone else falls in to the same problem. It is to do around data types and how they are related and possible data conversion that is required when upgrading.
What did you do?
I took a v4.11 database and upgraded it to the latest (7.4.3) using the Umbraco installer. There were a lot of custom or legacy data types being used by the old version. When opening the back-office, all of my legacy MNTP properties were empty. So, Umbraco obviously realised that there was a correlation between the two, but the data was partly lost in transit.
What did you expect to happen?
I expected the legacy MNTP picker values to still be present and correct on the updated Umbraco back-office.
What actually happened?
The legacy MNTP was set up to store it's values as XML, whereas the (v7) MNTP stores it's values as CSV. This meant that although Umbraco had switched my legacy MNTP data type to be the (v7) MNTP it hadn't converted any of the data associated to the properties.
In summary, no data was lost but I had to write a converter tool to map the data from XML to CSV. I can share this code with you if that helps. The data type screens for each is attached.
Backwards Compatible: True
Affected versions: 7.4.3
Due in version: