[BUG] Get-PnPTeamsTeam Only works with filters. Error Input string was not in a correct format

[ckravig]

Reporting an Issue or Missing Feature

When I run Get-PnPTeamsTeam alone I get an error. But it works when searching for a specific Identity or using a filter.

Expected behavior

When I run "Get-PnPTeamsTeam" I expect to see a list of all teams.

Actual behavior

What I actually get when running "Get-PnPTeamsTeam" is the error: Get-PnPTeamsTeam: Input string was not in a correct format. Failure to parse near offset 260. Expected an ASCII digit.

Running "Get-PnPTeamsTeam -Filter "startswith(mailNickName, 'IT')"" returns the teams, however running the base "Get-PnPTeamsTeam" returns the error.

Steps to reproduce behavior

After I connect I just run "Get-PnPTeamsTeam"

This was working as expected and then after running a few more commands trying to set teams settings, it started returing the above error. Many of the PnP cmdlets are returing this error now.

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

I have tried on 3.0, 3.1 and 3.1.10 nightly

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

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

[ckravig]

Because I eventually need to have this running in an Azure Runbook, I have installed PnP version 2.12.0 on my local machine (which was reccommended for Azure runbooks).

This seemed to have fixed the error for the time being.

[gautamdsheth]

hey @ckravig , can't reproduce this issue:

Can you provide more info about this ? Am executing the code in PS 7.5 , had also tested in 7.4 earlier and worked in both the cases. Possible that you might be loading an older version of the module. We had a similar issue reported in 2.99.x nightly builds which we managed to fix.

[ckravig]

Thanks for your reply @gautamdsheth, I don't have much more info about it.

What I can say is I have tried it in PS 7.2, 7.4, 7.5 with PnP v 3.0, 3.1, 3.1.1 nightly.

It initially worked on PS 7.5 with PnP 3.1 for a few hours then started replying with those errors repeatedly.

Once it no longer was working properly I started testing with other versions of PS and PnP and no combos of any of those versions I have listed worked.

I found out that it would work when filtering for teams but I really needed all the teams.

A coworker that was on an older version <3.0 (I don't know what version but I think it was close to 3.0 but older) had no issue.

At this point I wanted to move the script into Azure so following the guide here I was able to run the commands without error running on PnP 2.12.0.

Since that was working without error I downloading PnP 2.12.0 on my local machine with PS 7.5 and saw that I was no longer getting the errors.

That about the extent of the testing I was able to do as I need to continue with my project so I will be sticking with PnP 2.12 for now.

In total I have used PnP 2.12.0, 3.0, 3.1, and 3.1.1 nightly, so I am assuming the issue starts somewhere in 3.0 onward, but since I didn't test any version between 2.12 and 3.0 I am unsure if it exists in those as well.