Forum Discussion
Copilot Doesn’t Recognize Verified Answer After Setup
Hi,
I'm trying to use the new "Verified Answers" feature introduced in the May 2025 Power BI update under the "Prep Data for AI" section. I right-click on a visual in my report, select "Set up a verified answer", configure the settings, and click Apply. Initially, the defined question appears correctly under "All Verified Answers".
However, after closing and reopening the Verified Answers pane, the question I previously set up disappears, and Copilot fails to recognize or respond with the correct answer when prompted.
The report is using DirectQuery as the storage mode.
Is this a known issue or am I missing a step in the setup process? Any guidance would be appreciated.
Hi cosku_ersanli ,
You can follow these checks-
1.Q&A must be enabled in the model before you can author Verified Answers
2. Use the “Prep data for AI” ribbon in Power BI Desktop to manage them
3. Refresh the Copilot pane by closing and reopening it
Additionally you can go through the limitations mentioned in this document to check if you are missing something.
Prepare your Data for AI verified Answers
If the response has addressed your query, please Accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank You!
6 Replies
Hi cosku_ersanli ,
You can follow these checks-
1.Q&A must be enabled in the model before you can author Verified Answers
2. Use the “Prep data for AI” ribbon in Power BI Desktop to manage them
3. Refresh the Copilot pane by closing and reopening it
Additionally you can go through the limitations mentioned in this document to check if you are missing something.
Prepare your Data for AI verified Answers
If the response has addressed your query, please Accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank You!Hi v-sdhruv ,
Thank you for your response. Q&A was already enabled, but while reviewing the limitations, I identified the issue. The visual contained a calculated column that wasn't part of the semantic model. After replacing it with a different field from the model, the problem was resolved.
This actually is a bug. A lot of people are facing the same issue. Copilot team has identified it and a fix will be rolled out soon, probably by the end of next week. Stay tuned.
This is a known bug. The fix has been rolled out to July Power BI desktop. You should be good to go.
