How can I auto sync sharepoint excel files as basis for quick datasets?

Q&A
, ,
1

I have set up an AWS account for my organization with the shared goal of syncing files, trackers, etc to be utilized in quick for reports, analysis etc. Currently I cannot connect the S3 bucket as a datasource in Quick. This is creating an issue, requiring a manual weekly sync of 15 unique datasets. This could be greatly simplified by the ability to query our s3 bucket. The other option would be to allow sharepoint files as a source for datasets.

2

Hi @mhtcher

Welcome to the Quick community!

Amazon Quick Suite does support Amazon S3 as a native data source for datasets, so the manual weekly sync should be avoidable. The I can't connect the S3 bucket issue is most often a permissions/setup gap rather than a missing capability.

  • You create a small JSON manifest file that points to the S3 files or prefixes you want to pull, along with the upload settings.
  • Quick Suite reads the manifest and imports the file data into SPICE. (This path supports text files .csv, .tsv, .clf, .elf. Excel files use the separate file-upload path.)
  • Quick must be granted access to the bucket. If the bucket is in the same AWS account, this is an admin setting, if it’s in a different account, the bucket owner grants read access and you configure cross-account access, then reference it in the manifest.

The most common reason a connection fails is that Quick’s service role hasn’t been granted access to the bucket. Since you own the org’s AWS account, you can resolve this as the admin under Manage Quick -> Security & permissions -> Quick access to AWS services. Other frequent causes are insufficient IAM permissions (s3:GetObject, s3:ListBucket, s3:GetBucketLocation) or a bucket/service region mismatch, the troubleshooting guide below covers each.

On SharePoint it’s supported as an action connector and knowledge base (for search and Q&A), but it is not currently a structured dataset source for analytics, so S3 remains the recommended path for your reporting datasets.

Please refer to the following official documentation, which you may find helpful.