Forum Discussion
Preparing data for data agent
- 11 months ago
Hi Wickjone,
Thank you for reaching out to the Microsoft fabric community forum.
The data agent can read relationships defined in your lakehouse's semantic model via its schema. If it's struggling, ensure clear column names and permissions. Adding specific instructions in the agent's configuration can clarify joins, like: Table 'Sales' joins to 'Customers' on CustomerID (LEFT JOIN, one-to-many).Instructions are usually sufficient and more flexible than a single summary table. In the agent's settings, add table descriptions and Join logic. Example queries to guide the agent. A summary table is only needed for very complex scenarios.
The agent doesn't natively support partial matches (e.g: "Amy" for "Amy Burns"). Add instructions like: When asked for a partial name like "Amy", use SELECT * FROM Customers WHERE FullName LIKE '%Amy%'. Include example queries to train the agent.
Best regards,
Ganesh Singamshetty.
Hello Wickjone,
Hope everything’s going great with you. Just checking in has the issue been resolved or are you still running into problems? Sharing an update can really help others facing the same thing.
Thank you.
Hi, i would like to add on that adding the instructions to include wildcard characters for names is working as expected
what i did to improve the accuracy of the data is to denormalise the data to reduce to number of tables.
It made the data agent to process my queries faster and more accurate since it does not need to join many tables.