Dropdown prevalues are not applied when transfered from one env to another.

[HamDerAndrew]

When deploying changes the prevalues in the dropdown doesnt get sent over. Instead they leave the content blank when it has been successfully been transferred over.

Umbraco version

I am seeing this issue on Umbraco version: 7.15.6
Deploy version: 2.1.1

Reproduction

If you're filing a bug, please describe how to reproduce it. Include as much
relevant information as possible, such as:

Bug summary

I have a live environment with a Dropdown data type in a content node. The value is set to "Test 1".

If I then go to my dev environment and I create (or edit) a prevalue in the Dropdown data type and deploy to live, the
Dropdown value that I had on my content node on live, "Test 1", is set to blank.

This happens both in nested and non-nested content.

Specifics

Using Chrome v 87.0.4280.88 for Windows
Using Umbraco version: 7.15.6
Using Deploy version: 2.1.1

Steps to reproduce

1. Create a new project on Umbraco Cloud
2. Add development environment
3. Go to development environment and create some prevalues in the Dropdown editor under Developer -> Data Types -> Dropdown.

4. Create two Document Types. The first one holds your content, where you add a Dropdown property and a Nested Content property. Remember to make this node allowed as Root under "Permissions".

The second one ("Person" in this case) is your Nested Content. Add a Dropdown property here as well. I also added "Person Name" and "Person Age" just for illustrative purposes.

5. Create your test content. Remember to set a value in the Dropdown both for Nested and non Nested Content

6. Deploy and transfer content to your live env. Great, the content should be there together with the selected prevalue ("Test 1" and "Nested Prevalue 1" in this case) so it looks just like the image above.

7. Go to your dev environment and delete a prevalue in the Dropdown editor (I delete "Test 2" in this case) and save the changes. My prevalues on dev now look like this:

8. Deploy your changes from dev to live.
9. Your live environment should now have lost the prevalue in the Dropdowns so it looks like this:

This happens whether you remove, add or edit a prevalue.

Expected result

The prevalues should still be there unless they are actively changed on the dev environment and pushed to the live environment

Actual result

The prevalues are empty

[nul800sebastiaan]

Thanks I've moved this to the Cloud tracker to be picked up as a Deploy issue.

[AndyButland]

Attempted to replicate this on CMS v8 / Deploy v4 and not seeing the issue. Could well still be a problem in CMS v7 / Deploy v2.

[dnwhte]

I have experienced this issue on v7 with Deploy 2.1.1.

[umbrabot]

Hiya @HamDerAndrew,

Just wanted to let you know that we noticed that this issue got a bit stale and might not be relevant any more.

We will close this issue for now but we're happy to open it up again if you think it's still relevant (for example: it's a feature request that's not yet implemented, or it's a bug that's not yet been fixed).

To open it this issue up again, you can write @umbrabot still relevant in a new comment as the first line. It would be super helpful for us if on the next line you could let us know why you think it's still relevant.

For example:

@umbrabot still relevant
This bug can still be reproduced in version x.y.z

This will reopen the issue in the next few hours.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

[TomChancer]

@umbrabot still relevant
After the release of 16.0.3 fixing up the null properties from V7 to V13/16 migrations, it became apparent this bug looks like it impacts Migrations from V7 to later versions.

Currently, it looks like V7 artifacts which stored values as a ;; delimited string cant get applied to the published version on later Umbraco versions, even after including the Legacy Property Migrators or manually altering the value on an Artifact by swapping it to a JSON Array as expected.