Forum Discussion
Preparing data for data agent
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.
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.