Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! It's time to submit your entry. Live now!
I want to display the revenue per category per month in 2024. There are 3 categories and 12 months. When I do a query in SQL Analytics endpoint, it returns 36 rows in full. However, when I do a prompt in Fabric Data Agent, it only returns 25 rows. I want to display all rows because I want to display it as a clustered bar chart in copilot studio using quickchart. What should I do?
Solved! Go to Solution.
Hi @margaretaak , Thank you for reaching out to the Microsoft Community Forum.
You’re right, the Fabric Data Agent isn’t meant to act like a full data endpoint. It’s designed for conversational insights, not for returning complete datasets. As a result, it automatically limits or summarizes rows in its chat responses to keep things concise and performant.
If you need to visualize all 36 rows, the best approach is to have the agent store your query results in a Lakehouse table or dataset, then connect Quickchart or Copilot Studio directly to that source so you can work with the full dataset.
Hi @margaretaak , Hope you're doing okay! May we know if it worked for you, or are you still experiencing difficulties? Let us know — your feedback can really help others in the same situation.
Hi @v-hashadapu
If that's the case, then it's no longer a fabric data agent. This means there's no way for a fabric data agent to display more than 25 records?
Hi @margaretaak , Thank you for reaching out to the Microsoft Community Forum.
You’re right, the Fabric Data Agent isn’t meant to act like a full data endpoint. It’s designed for conversational insights, not for returning complete datasets. As a result, it automatically limits or summarizes rows in its chat responses to keep things concise and performant.
If you need to visualize all 36 rows, the best approach is to have the agent store your query results in a Lakehouse table or dataset, then connect Quickchart or Copilot Studio directly to that source so you can work with the full dataset.
Hi @margaretaak , hope you are doing great. May we know if your issue is solved or if you are still experiencing difficulties. Please share the details as it will help the community, especially others with similar issues.
Have you added any custom instructions or example queries? If so check those in the first instance.
Dear @KevinChant
Yes, I have added this instruction "do not limit the number of rows returned, return all rows". For example queries, I have added the query I used in SQL Analytics endpoint but it does not change anything. What should I do?
Regards,
Margaretaak
Hi @margaretaak , Thank you for reaching out to the Microsoft Community Forum.
The difference you’re seeing isn’t caused by your SQL query, it’s because of how Fabric Data Agent handles query responses. The SQL Analytics endpoint will always return all rows you query (in your case, 36 rows) but the Data Agent isn’t designed to return full data tables in its conversational responses. It automatically applies a row limit, typically around 25 to keep interactions concise and performant. Adding natural-language instructions like do not limit the number of rows returned doesn’t override that internal cap.
The only way to get all 36 rows visible for visualization in Copilot Studio with Quickchart is to avoid having the Data Agent directly return the data. Instead, tell it to store the query result in a Lakehouse table or dataset and then have Quickchart connect to that dataset or to the SQL Analytics endpoint directly. This approach ensures the visualization uses the complete result set and not the truncated conversational response.
Query the SQL analytics endpoint of your SQL database - Microsoft Fabric | Microsoft Learn
Fabric data agent creation (preview) - Learn how to create a Fabric data agent | Microsoft Learn