Install-SPOSolution returns error "Invalid Field Name" about pnp-powershell

[erwinvanhunen]

I will close this issue as the issue as such is not related to the cmdlet functionality. The cmdlet merely uploads the solution using the core library. Effectively the cmdlet is one line of code:

ClientContext.Site.InstallSolution(PackageId.Id, SourceFilePath, MajorVersion, MinorVersion);

However, the Guid is most likely the ID of the field in question.

If you use the cmdlets to connect to the target site, you can retrieve the field in question with:

Get-SPOField -Identity 33e33eca-7712-4f3d-ab83-6848789fc9b6 

In the core library we use the DesignPackage classes to upload and activate the solution. While this most of the time works, it's not a given that it works in every environment or with every solution package, as the DesignPackage classes are specifically targeted toward, as the name says, Design Packages. As those are sandboxed solution packages as such, we found that in our test cases the functionality also works with other sandboxed solution packages.

I recommend you to create an issue in the officedev/pnp-sites-core repository if your issue remains.

[valtynikov]

@hanielc did you figure out what was the issue? I'm getting an exact same error message when trying to install a sandbox solution.

[hanielc]

@valtynikov, no I was not able to figure it out. I ended up using native CSOM code to get it to work.

[MavJutras]

This seems to be an issue with many users, is there a place for support as to why this will not work. From the manifest you can pull out the solution id but it reverts to saying that it has an invalid field name and seems to be the same for the two already on this thread.

[MartinHatch]

I was getting this issue when the WSP was already in the Solution Gallery and I was running the PnP function for the first time.

Deleting the WSP so it is uploaded fresh via PnP-PowerShell resolved it.