[BUG] Pnp-term commands on pinned terms issue
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 904
- Forks
- 407
- Avg merge
- 9h 16m
- Merged PRs (30d)
- 10
Description
Reporting an Issue or Missing Feature
Issue
Expected behavior
Move-PnpTerm on a term that is pinned in another termgroup should move the term to the destination
Set-PnpTerm -deprecate should set the term to deprecated
Actual behavior
got an error message : The operation is not valid on the pinned term
Steps to reproduce behavior
Pinned manually a term to another termgroup and try to use the following command:
Move-PnPTerm -Identity -TargetTerm -MoveToTerm
Set-PnPTerm -Identity -Name -TermSet -TermGroup -Deprecated $true
What is the version of the Cmdlet module you are running?
I tried 2.2, 2.12 3.1
Which operating system/environment are you running PnP PowerShell on?
- Windows
- Linux
- MacOS
- Azure Cloud Shell
- Azure Functions
- Other : please specify
I’ve many terms in a Termgroup that are pinned to another termgroup. Using PnP cmds on those pinned terms result to an error message: The operation is not valid on the pinned term
I can understand this limitation, but this behaviour is exclusive to one of my 3 tenants and seems to imply we basically cannot do anything an a term at the moment it's pinned somewhere else.
Authentication method : interactive or by apps & certificate
When I remove the ‘link' to the terms from the secondary termgroup, it’s working as expected.
When I recreate pin, the issue come back.
Structure of terms, Ids, Name, creation method, pinned method are aligned on all 3 tenants.
Doing it via graphical interface is working well
I would like to ask for any help or similar experience related to it in order to identify the cause and avoid the same behavior to be propagate in my others tenants
Thank you in advance,
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Move-PnPTerm and Set-PnPTerm commands against a term pinned in another term group, comparing the failing tenant with the tenants where they work. Trace the command entry points and the handling of the “operation is not valid on the pinned term” response; done means both commands support the reported pinned-term cases without breaking existing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100