I created 2 separate Knowledge Bases associated with 2 Sharepoint Integrations last week and added OneNote Notebooks that I have hosted on the Sharepoint site. I have not been able to have the KB Sync processes identify and Add the OneNotes to the Knowledge Bases. I have tried removing and re-adding the OneNote files to the Knowledge Bases but still the Sync processes will not add the files. I am migrating a lot of business management information for my team from Quip and organizing into OneNote files and this is going to be key to making my Chat Agents useful.
I see in that the Quick Suite documentation was updated over the last week and and now references OneNote files as in scope to be included in this type of Knowledge Base. How do I get the KB Sync process to identify and Add the OneNotes to the Knowledge Bases? I am hoping I don’t have to create a new Knowledge Bases in the Sharepoint Integrations for my Spaces.
So, when you are migrating files are you receiving any error messages? That could be what is holding up the sync process. Something else is that while OneNote is a supported content type, you may not have full permissions to access it within your integration.
If you’re still having issues after checking these, could you share any potential error messages you are receiving?
Hi @JacobR, I am a site owner for the Sharepoint site and I created the OneNote files directly in the Sharepoint document library that the other files in my KB reside. I am not seeing any errors when I work with the OneNote files and I have full access.
I am working with a colleague who suggested putting the OneNote file in it’s own Sharepoint folder so I currently have one KB setup with a OneNote file itself selected to be included and the other KB that includes the folder that only the other OneNote file resides in. In both cases the Sync does not Add the OneNote file and I’m not seeing any errors in the Sync reports produced.
Thank you for the additional context. I am unsure why the OneNote files are not syncing over through the integration. One thing you can do is review the integration documentation to ensure you did not potentially miss any steps in the integration process that might be causing the issue (Microsoft SharePoint integration - Amazon Quick). If you do not see anything from that, then I would recommend submitting a support ticket and the support team will be able to further investigate to what may be the cause. Please refer to this resource on how to submit a support ticket (Case management - AWS Support).