Closed paxvas closed 1 day ago
hi @paxvas , starting with tomorrow's nightly builds, you will be able to set the contributors and managers of the term group via New/Set-PnPTermGroup cmdlets.
Have updated the docs as well around this with an example.
The PnPTermGroupToXml
cmdlets already support exporting and importing them.
Thanks for raising this feature request.
Hi Team,
thank you for the good news :-) appreciate your work.
Kind regards janko
Am Do., 21. Nov. 2024 um 21:18 Uhr schrieb Gautam Sheth < @.***>:
hi @paxvas https://github.com/paxvas , starting with tomorrow's nightly builds, you will be able to set the contributors and managers of the term group via New/Set-PnPTermGroup cmdlets.
Have updated the docs as well around this with an example. The PnPTermGroupToXml cmdlets already support exporting and importing them.
Thanks for raising this feature request.
— Reply to this email directly, view it on GitHub https://github.com/pnp/powershell/issues/4525#issuecomment-2492186216, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN6ZZQUZOSUVPPTSRICJEQT2BY52VAVCNFSM6AAAAABRKVMIMKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJSGE4DMMRRGY . You are receiving this because you were mentioned.Message ID: @.***>
If I want to update multiple Site Collection Termgroups to have a specific Termgroup admininistrator I can do this only via the web interface or via PnP Template import. This is frustrating if I have to update many Sites. Furthermore selfservice automation scenarios are difficult to achive.
The solution would be to add a new parameter -TermGroupAdmin certain Termgroup Cmdlets:
where I can specify a user or group who should be the administrator of this group. With this new parameter I could batch update Site collection term groups and build selfservice automation scenarios like "Set Termgroup admin for Site Collections I own" etc.
Microsoft SPO Management Shell is also not supporting this option.