Applies to Product - Microsoft Copilot Studio
What’s happening?
The customer is seeking guidance on how to obtain bot topics utilized in conversations (live chat) between visitors and the Copilot Studio bot within the CRM system.
What’s happening?
The customer is seeking guidance on how to obtain bot topics utilized in conversations (live chat) between visitors and the Copilot Studio bot within the CRM system.
Reason:
Topics in Copilot Studio are not stored in an independent Dataverse table. Instead, they exist as a type under the Copilot Components table without actual content being stored there. The topic definitions and values remain within Azure cloud DB as part of the Bot Framework Composer, making topic data inaccessible for direct retrieval.
Topics in Copilot Studio are not stored in an independent Dataverse table. Instead, they exist as a type under the Copilot Components table without actual content being stored there. The topic definitions and values remain within Azure cloud DB as part of the Bot Framework Composer, making topic data inaccessible for direct retrieval.
Resolution:
Due to the limitations of the current system, writing plug-in codes to read the topics utilized in a conversation (live chat) between a visitor and the Copilot Studio bot is not feasible at this time. It was suggested to create a custom Topics entity to audit and record all utilized topics within a specific conversation; however, the challenge lies in detecting the Conversation ID in Copilot Studio and using Power Automate to store this value in the custom Topics table. Currently, Copilot Studio does not provide a direct way to retrieve the Conversation ID, and there are no built-in expressions or variables that allow direct access to it. The only feasible approach is to generate and store a custom GUID as a workaround for the conversation ID.
Due to the limitations of the current system, writing plug-in codes to read the topics utilized in a conversation (live chat) between a visitor and the Copilot Studio bot is not feasible at this time. It was suggested to create a custom Topics entity to audit and record all utilized topics within a specific conversation; however, the challenge lies in detecting the Conversation ID in Copilot Studio and using Power Automate to store this value in the custom Topics table. Currently, Copilot Studio does not provide a direct way to retrieve the Conversation ID, and there are no built-in expressions or variables that allow direct access to it. The only feasible approach is to generate and store a custom GUID as a workaround for the conversation ID.