If Topic 2 is triggered by a sentence written in Topic 1, both the Initial User Message and Topic Name in the Sessions log is properly identified;
However, if Topic 2 is reached through a redirection after a button was clicked in Topic 1, the Initial User Message in Sessions log is properly set to be the text of the button, but the Topic Name is empty.
Any idea on how to fill the Topic Name in this second case?
Topic Name not identified when topics are launched from a redirection
Thanks for your answer @@SaiRT14 I guess the important action here is when you mention "update the session log". How can I do that? I tried to set System.Recognizer.TriggeringMessage.Id = System.LastMessage.Id and System.Recognizer.TriggeringMessage.Text = System.LastMessage.Text but Copilot Studio gives me an error.
Is there any other way I can modify the session log to force Copilot Studio to treat this information as a triggered Text Event?
Topic Name not identified when topics are launched from a redirection
when redirecting from Topic 1 to Topic 2 using a button, the analytics log recognizes the button text as the initial user message but does not associate the session context with Topic 2 unless it is explicitly configured to do so. Here's how you can resolve this:
Use the "Redirect to Topic" Action Properly Ensure that the button in Topic 1 uses the "Redirect to another topic" action. When configuring the button: Click on the button in Topic 1. Choose the "Redirect to Topic" action. Select Topic 2 explicitly from the dropdown.
In Topic 1, add a custom variable action - SetVariable("redirectToTopic", "Topic 2")
In Topic 2, check for this variable in the topic trigger conditions or use it to update the session log.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
2
Share
Report
All responses (
Answers (
