Sharepoint Connector Site Limitation

[TX-Aggie-00]

Hey All!

We are trying out the Beta connector for SharePoint and found that the connector will not work at the root-level site.  Is there a reason for this limitation.  It is unfortunately a hard blocker for us to use the native connector.  

MUST_START_WITH_SITES

Path must start with '/sites/' or '/teams/', got 'pathComponent'.

Do anyone know if this is just a beta limitation and, if so, if it will be removed in the future?

Thanks,
Scott

[saravjeet]

How you have made the connection, the reason I am asking because, We have two separete tenants (sharepoint in a separate tenant) and databricks setup in a differenet tenant, at the moment we are using the logic app to bring the data into the platform. I know we need to have a principal who have the access to the sharpoint tenant but in our case, IT teams are not allowing to grant the access which is required to pull the data and we are looking for the ways how to bring the data and what are the possible solutions around it. Thanks. 

[TX-Aggie-00]

Hey Saravjeet, we are currently working in the same tenant.  Not sure the connector has an issue with tenant to tenant but we had to revert to graph api's to sync.  We are still using logic apps to capture deletes and add those to a storage queue.  We have race condition logic to accommodate both processes and that would still be the case if we used the connector, since deletes are not captured (as far as I can tell).

Thanks
Scott

[emma_s · Accepted solution]

Hi Scott,

Just asking our product team the quesiton. By the root level site do you mean content that is stored on the root level site? Or do you mean everything across your root tennant. ie you want to ingest all files across your tennant in a single pipeline? If its the root tennant then they will be building support for this in the managed connector hopeully launching next quarter.

Thanks,

Emma

[TX-Aggie-00]

Thanks Emma, yes, most of our clients store documents in folder in the root level site, so we will never have the path /site/{sitename} in the sharepoint path.  This is was triggers the error I shared.

I look forward to that release in the near future.  Will certainly streamline a lot of processes!

Appreciate the response and letting me know!
- Scott