ok i confirm : there was a silent update from Microsoft, wich oblige to use folder
here i will show in my agent
first : i try to reproduce you'r case: same error
and here the same document library, added to another agent 2 month ago
so Microsoft made a silent update and force people to use folder for both solution, it's software lock to refuse the root of document library at the moment
hum interesting, i didn't notice before because , since i making agent everyday, i recommand to don't use the "root" of document library.
I recommand to have at least few folder in document library and add few sharepoint knowledge source for each of those folder, it will allo you to teach the agent wich folder are "what for" because the orchestration use the folder description in the agent. So to my mind , for the way i do agent, it's not a big deal (but i understand it could be frustrating)
i deeply recommand to use few folder and add few knowledge source sharepoint for roots folder, it really help the agent to give better result with understanding of the content :)
So "WHY" you have this error :) ?
my opinion since i m not a MSFT insider :)
recently we got this update in sharepoint knowledge source :
wich allow to have filter.
technicaly : folder are based on the same technical "element" called the "ITEM" (it's a technical part of the sharepoint element since sharepoint is a things 20 years ago)
But a document libary is something else -> so it's impossible to apply those filter on the element "document libary", only on folder and "document".
so this explain totaly the error message and the bug :) i think soon microsoft will correct the error message :)
if this help to resolve you'r case please mark the answer as verified it's important for the community
