Reporting on Copilot Studio data

Hi team,

I am looking for some guidance on reporting on my Copilot analytics data.

I have downloaded and customise the template which was originally for PVA, however I am getting discrepencies in my data when connecting to my DEV and UAT environments.

In DEV, the report seems to work and pick up my topics as expected, however in UAT it returns blank data for all my topics.

After doing some digging I can see that the content logs in the ConversationTranscript table follows different formats, one includes fields such as topicId, whereas the other contains the taskDialogId.
Why is this? It seems like some some of my data data in dev contains the taskDialogId, but other records only have topicId.

This means when I am looking to customise my report in Power BI, the original logic from the template does not point at the taskDialogId information.

Please can I get some guidance on what the correct approach is? I have spoken with Microsoft who advised I should be using the new conversation KPI module. Is this something that I can customise further myself, and is this the recommended approach for reporting in Power BI? Should I look into alternatives like Azure app insights?

Many thanks in advance!
Chloe

Start by comparing the DEV and UAT records in the ConversationTranscript table, especially the topicId and taskDialogId fields, and review the downloaded Power BI template's original logic. Then examine the conversation KPI module and the Azure Application Insights alternative; done means documenting the recommended reporting approach and how the differing record formats should be handled.