Information
- Products: Sparkrock 365
- Summary: File attachments that exceed the maximum size of 350MB.
Details
By default, Sparkrock 365 (Business Central Online) limits the maximum size of file attachments to 350MB. If you attempt to upload a file attachment that exceeds this limit, the upload will fail with an error message “Upload did not compete within the 65 seconds time limit. The maximum file size is 350 MB”.
Resolution
There are several ways to deal with file attachments that exceed the maximum size of 350MB in Sparkrock 365:
Depending on the file you want to attach, if it’s large, one option is to
- Save it in a shared location or cloud e.g SharePoint, OneDrive etc. And attach the access link within the system instead of attaching the file directly.
- In the repository, you can manage the security of your files. For confidentiality issues, uploading the files first to a repository is better than attaching the files directly into Sparkrock 365.
Impact/Risk
A file of more than 350 MB is quite large and attaching many files of this size will quickly increase database size, which coud have a performance impact to your Sparkrock 365 environment.
Large files impact the size of the database and generate additional costs if you’re hosted in Azure or some other cloud for more storage capacity.
Workaround
If you none of the above methods solve the large file attachments issue, you may want to consider splitting the file into smaller chunks, compressing the file to reduce its size, or removing unnecessary data from the file.
Related Information
Microsoft has published a guide on how to manage file attachments in Business Central Online. You can access it here: https://docs.microsoft.com/en-us/dynamics365/business-central/admin-manage-attachments
Update History
Date | Details | Link |
05/29/2023 | The first version of this Knowledge Base article was created. |
|
Attachment
“Not Applicable”
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article