CustomScriptSafeDomains.Create returns "Cannot convert the "Microsoft.SharePoint.Client.ScriptSafeDomainEntityData"

[djsladi]

Reporting an Issue or Missing Feature

Error when trying to set HTML field security using latest PnP & SharePoint Online Management Shell

Expected behavior

Domain should be added to HTML field list

Actual behavior

Cannot convert argument "parameters", with value: "Microsoft.SharePoint.Client.ScriptSafeDomainEntityData", for "Create
" to type "Microsoft.SharePoint.Client.ScriptSafeDomainEntityData": "Cannot convert the "Microsoft.SharePoint.Client.Sc
riptSafeDomainEntityData" value of type "Microsoft.SharePoint.Client.ScriptSafeDomainEntityData" to type "Microsoft.Sha
rePoint.Client.ScriptSafeDomainEntityData"."

Steps to reproduce behavior

$Domain = [Microsoft.SharePoint.Client.ScriptSafeDomainEntityData]::new()
$Domain.DomainName = "test.com"
Connect-PnPOnline -Url $siteColl -Interactive
$site = Get-PnPSite -Includes CustomScriptSafeDomains
$site.CustomScriptSafeDomains.Create($Domain)

What is the version of the Cmdlet module you are running?

1.9.0

Which operating system/environment are you running PnP PowerShell on?

• Windows
• Linux
• MacOS
• Azure Cloud Shell
• Azure Functions
• Other : please specify

[gautamdsheth]

Seems to work fine at my end, can you please try with the latest 1.10 version as well and check ?

You also need to execute Invoke-PnPQuery after $site.CustomScriptSafeDomains.Create($Domain) to add this to the field security list.

[djsladi]

No, it's not working... :-(

Seems to work fine at my end, can you please try with the latest 1.10 version as well and check ?

You also need to execute Invoke-PnPQuery after $site.CustomScriptSafeDomains.Create($Domain) to add this to the field security list.

[katjones23]

I'm receiving the same error today with the same syntax @djsladi has, though it worked fine yesterday.

[katjones23]

I have a work around that appears to be working consistently at this time:

$Site = Get-PnPSite -Includes CustomScriptSafeDomains 

$object = [PSCustomObject]@{
       DomainName = <#Domain name goes here#>
}

$Site.CustomScriptSafeDomains.Create($object)

[djsladi]

I have a work around that appears to be working consistently at this time:

$Site = Get-PnPSite -Includes CustomScriptSafeDomains 

$object = [PSCustomObject]@{
       DomainName = <#Domain name goes here#>
}

$Site.CustomScriptSafeDomains.Create($object)

This one did the trick, thank you very much! :-)

[gautamdsheth]

hi @djsladi , @katjones23 - we have added a new ScriptSafeDomainName parameter to set-pnpsite cmdlet.
It will be available from tomorrow's nightly builds and the next major version
Am closing this issue hence.