Microsoft.Graph.Reports - Get-MgReportTeamUserActivityCount

[JohanssonMarkus]

Get-MgReportTeamUserActivityCount -Period "D7" Give an error

PS H:> Get-MgReportTeamUserActivityCount -Period "D7"
Get-MgReportTeamUserActivityCount : Expected '{' or '['. Was String: Report.
At line:1 char:1

• Get-MgReportTeamUserActivityCount -Period "D7"

•   + CategoryInfo          : NotSpecified: (:) [Get-MgReportTeamUserActivityCount_Get1], ParserException
    + FullyQualifiedErrorId : Microsoft.Graph.PowerShell.Cmdlets.GetMgReportTeamUserActivityCount_Get1 
  

AB#7395

[MIchaelMainer]

This is a known issue where the metadata describes this as JSON and the response is csv.

[JohanssonMarkus]

@MIchaelMainer Ok good to know, when will it be solved?

[MIchaelMainer]

We don't have this scheduled yet on our side, and I'm unaware what the story is on the server side for this API set. This scenario requires the use of Invoke-GraphRequest for now.

[joshtransient]

Also adding that the cmdlets in Microsoft.Graph.Reports fail when the file specified by -OutFile doesn't already exist.

[darrelmiller]

I was able to repro this issue:

C:\src\msgraph-sdk-powershell [dev ≡ +4 ~2 -0 !]> Get-MgReportTeamDeviceUsageUserCount -Period "D7" -OutFile report.txt
Get-MgReportTeamDeviceUsageUserCount_Get: Cannot find path 'C:\src\msgraph-sdk-powershell\report.txt' because it does not exist.

[georgend]

@JohanssonMarkus
A workaround for now would be to use Invoke-MgGraphRequest
The following options:-

-InferOutputFileName :- Infer the output file name and store it in the current directory.

Connect-Graph -Scopes @("Reports.Read.All")
Invoke-MgGraphRequest -Uri "https://graph.microsoft.com/v1.0/reports/getTeamsUserActivityUserDetail(period='D7')" -InferOutputFileName

-OutputFilePath :- specify the name of the output file.

Connect-Graph -Scopes @("Reports.Read.All")
Invoke-MgGraphRequest -Uri "https://graph.microsoft.com/v1.0/reports/getTeamsUserActivityUserDetail(period='D7')" -OutputFilePath report.csv

You can substitute the -Uri with

• https://graph.microsoft.com/v1.0/reports/getTeamsUserActivityCounts(period='D7') for getTeamsUserActivityCounts
• https://graph.microsoft.com/v1.0/reports/getTeamsUserActivityUserCounts(period='D7') for getTeamsUserActivityUserCounts

[peombwa]

The OpenAPI document currently represents the content-type of this response as application/json instead of application/octet-stream. To solve this, we need to ensure that all content-types of report functions are accurately represented in the converted OpenAPI. Without this, code generators won't be able to know how to properly handle responses.

Currently

This in CSDL:

Gets converted to this in OpenAPI:

Expected

For the cmldet to function as described in MS Graph docs, we need to ensure that the response is describes as shown below:

cc\ @ddyett , @darrelmiller, @mairissi: Should we address this in the metadata or let DevX API handle it.

[chenxizhang]

some error here, do we have plan to fix the issue?

[peombwa]

This is being tracked here https://github.com/microsoftgraph/microsoft-graph-devx-api/issues/552 and will be fixed via XSLT transform.

[weyCC81]

This is still happening with Module "Microsoft.Graph" at Version "1.7.0", please fix

[silijon]

From what we can tell, the Microsoft.Graph.Reports module is comprehensively broken because of this issue. It's been outstanding for a while. If it can't be fixed on the metadata side, is there any thought to having additional api metadata transforms applied prior to the sdk generation? That would at least insulate the sdk from inheriting upstream problems that can't be fixed for years at a time....

[maisarissi]

Hi @silijon . We have been working with other teams to get this fixed.
As you can see here the team managed to fix and now we are just waiting for the next version release to be out so we can validate on our side.
Once we get this done, we will update and close this issue.