You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Details of the scenario you tried and the problem that is occurring
A Sensitivity Label has an Advanced Setting called 'contenttype'. In this property, the locations where this label can be used is stored.
When exporting a label, this property is also exported, but when importing the resource, the contenttype property is ignored.
As it turns out the New/Set-Label cmdlets have a dedicated ContentType parameter which has to be used instead.
Verbose logs showing the problem
Suggested solution to the issue
Change the resource to use the ContentType parameter instead of the AdvancedSettings. Also filter the contenttype property during export.
The DSC configuration that is used to reproduce the issue (as detailed as possible)
# insert configuration here
The operating system the target node is running
Version of the DSC module that was used ('dev' if using current dev branch)
dev
The text was updated successfully, but these errors were encountered:
Details of the scenario you tried and the problem that is occurring
A Sensitivity Label has an Advanced Setting called 'contenttype'. In this property, the locations where this label can be used is stored.
When exporting a label, this property is also exported, but when importing the resource, the contenttype property is ignored.
As it turns out the New/Set-Label cmdlets have a dedicated ContentType parameter which has to be used instead.
Verbose logs showing the problem
Suggested solution to the issue
Change the resource to use the ContentType parameter instead of the AdvancedSettings. Also filter the contenttype property during export.
The DSC configuration that is used to reproduce the issue (as detailed as possible)
# insert configuration here
The operating system the target node is running
Version of the DSC module that was used ('dev' if using current dev branch)
dev
The text was updated successfully, but these errors were encountered: