Forum Discussion
Usage metrics: I see many differents GUID for one report
Hello, I have created a reporting based on "Report Usage Metrics Model". My question is that I see many GUIDs for each of my reports. In this example screenshot, the same report has 2 differ...
I see a similar issue.
In our case:
- each of the 5 reports on our single workspace have multiple (from 3 to 10) Report GUIDS listed in Usage Metrics
- however, only 2 GUIDS per Report Name have views (and View Count seems pretty balanced between each pair)
- I can succesfully open a report by replacing a GUIDs in URL.
- However I cannot download or edit one of the report and it seems that it's a different version, as some numbers are mismatched. The workspace is the same, report name is the same (but there is only 1 report in actual workspace)
- Multiple GUIDS appear only for those reports, which are accessed via the app.
- Note - those reports also using a shared dataset
- In our solution there are 3 other workspaces where each report has its own dataset, but none of them have this issue
- Additionally, we try to levarage Power BI REST API combined with Log Analytics, and I found out:
- Power BI REST API retrieves just one GUID per report name in a workspace group (retrieved GUIDS are associated with reports visible on the workspace)
- However, Log Analytics shows a data for both GUIDs, therefore joining two datasets results in blank attribute names for many query executions logged
- With Log Analytics I found that users who access report via 1st GUID are developers/managers with higher than "Viewer" capabilities, whereas 2nd GUID is associated to users regular users (could that be an app that generates another report GUID...? It's not appearing on the app, though)
Can anyone advise?
Were you able to find a solution for this issue? I'm also getting two different guids for the same report in Log Analytics and then when I use the REST API to get the report data I only get the information for the GUID that is presented in Service when I open the report, which doesn't allow me to get the report name in a proper way to analyze more efficientely the Log Analytics data.