Skip to content

[BUG] Inconsistent documentation and implementation for Add-PnpTermToTerm #3888

@mappinger

Description

@mappinger

Reporting an Issue

Add-PnpTermToTerm wrong parameters in documentation

Expected behavior

In the documentation (https://pnp.github.io/powershell/cmdlets/Add-PnPTermToTerm.html) for the cmdlet Add-PnpTermToTerm is a parameter "ParentTerm" listed.

Actual behavior

There is no parameter ParentTerm, only ParentTermId. Providing only the ParentTermId creates a ChildTerm in the wrong term set (because the Parent Term is reused in different term sets).

Steps to reproduce behavior

$parentterm = Get-PnpTerm -TermSet {{guid}} -TermGroup {{guid}} -Identity {{guid}}
Add-PnpTermToTerm -ParentTerm $parentterm -name "Test" -lcid 1031

Error Message:
Add-PnPTermToTerm: Cannot bind parameter 'ParentTermId'. Cannot convert the "Microsoft.SharePoint.Client.Taxonomy.Term" value of type "Microsoft.SharePoint.Client.Taxonomy.Term" to type "System.Guid".

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

2.4.0

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

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions