pnp / pnp/pnpframework

Invoke-PnPSiteTemplate - the field was found invalid

Open
#658 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
259
Forks
161
Avg merge
10h 33m
Merged PRs (30d)
1

Description

I am trying to apply a pnp site template using the PnP PowerShell. It is failing for two of my customers, but works on my machine frustratingly.

It fails with a 'field was found invalid' error, I have checked the template thoroughly and I cannot find any culprits.

WARNING: ListInstance Style Library is a Style Library of a site with NoScript enabled and will be skipped
Failed to configure the SharePoint site {0} The field was found invalid:
At C:\Users\adm_e606495\Desktop\New folder\Source\Scripts\deploy.ps1:671 char:9

  • throw('Failed to configure the SharePoint site {0}', $_.Excep ...
  • CategoryInfo : OperationStopped: (System.Object[]:Object[]) [], RuntimeException
  • FullyQualifiedErrorId : Failed to configure the SharePoint site {0} The field was found invalid:

This worked a while ago but suddenly seems to have stopped working, I have tried previous versions of PnP PowerShell (back to 1.8.0) with the same issue.

Any ideas?

Thanks

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Invoke-PnPSiteTemplate entry point and the deploy.ps1 call at line 671, then reproduce the failure using the affected site template and a customer environment. The issue does not include the template or identify the invalid field, so the work is complete only when the failing field and a reliable fix or reproduction are documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, powershell
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.