Forum Discussion
SharePoint doc library metadata columns
I'm adding a SharePoint site pages library as a knowledge source. The library has several metadata columns. There's a lot of "knowledge" stored in those columns I need Copilot to consider but it seems to ignore them completely.
Is there a way to get Copilot to use the columns for information?
5 Replies
I'm curious if you ever found a solution for getting the metadata from a document library. We have a use case/desire for this, but so far I've not found a way to use it. Given your note on the declarative agent not working, I'm hopeful you might have found another way.
Did you find any workaround using copilot studio?
That's cool that a declarative agent was able to created to handle it, but it shouldn't be necessary. We have managed metadata for 'Account' and have tagged files across multiple sites. Copilot isn't paying any attention to the tagging. I was hoping that if it was centralized/global metadata, rather than stand alone columns, it would help. So far, no difference.
You're right. On further investigation my above solution didn't work for a standard document library, but it did work for a site pages library. I'm not sure why. I'm still troubleshooting.
I was able to resolve this by creating a declarative agent in visual studio code instead of copilot studio.
https://learn.microsoft.com/en-us/microsoft-365-copilot/extensibility/build-declarative-agents?tabs=ttk
