[BUG] Can't rename existing term with a localeid
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
Updating the Name of the designated Term for the english translation using this command :
Set-PnpTerm -Identity "ID of Term" -Name"New Name" -TermSet "My term set" -TermGroup "My term Group" -Lcid 1033
Actual behavior
It is ignoring Lcid parameter and renaming french translation
It is very Odd because if i use same command but replace -Name by -Description, here it is working as expected, english description is changed...
Steps to reproduce behavior
Use Set-PnpTerm -Identity "ID of Term" -Name"New Name" -TermSet "My term set" -TermGroup "My term Group" -Lcid 1033
On a term that as French and English translation set.
What is the version of the Cmdlet module you are running?
2.12.0
Which operating system/environment are you running PnP PowerShell on?
- Windows
- Linux
- MacOS
- Azure Cloud Shell
- Azure Functions
- Other : please specify
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 Set-PnpTerm command from the issue on a term with French and English translations, comparing the -Name and -Description behavior for -Lcid 1033. Trace the Set-PnpTerm implementation and its locale handling; done means the command updates the English name without changing the French translation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- cli, localization
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100