Hi @Iain White Greetings! Thank you for posting this question here.
values from a previous deployment are being applied and are overwriting any new properties I apply
I suspect the previous deployment is still targeting the device and applying the settings. You can validate this by inspecting the Metrics captured from the deployments and verify if it still being applied to the device. Also, please make sure that the new deployment has a greater Priority number. Kindly note that if an IoT Edge device is targeted by more than one deployment, the deployment with the highest priority applies.
If you prefer to remove any existing desired properties from the previous deployments, you can perhaps do so by setting the desired property to null
in the latest deployment. This recommendation is based on the observations from Back end operations from module twins where the following sample is provided on how to remove a desired property.
{
"properties": {
"desired": {
"newProperty": {
"nestedProperty": "newValue"
},
"existingProperty": "otherNewValue",
"otherOldProperty": null
}
}
}
The documentation is a bit difficult to understand
Thank you for bringing this feedback to us. We will work on improving the article to provide clarification.
there doesn't appear to be any way to tell if a deployment is layered or not from the portal
We will check with the team internally on this and get back to you with more updates.
Please let us know if you have any additional questions or need further clarification in the comments below. We would be glad to help you further.
If the response helped, please do click Accept Answer and Yes. Doing so would help other community members with similar issue identify the solution. I highly appreciate your contribution to the community.