Release Date: May 28, 2026
Summary
- Corrupt files in SharePoint — large files over approx. 8 MB were damaged during journalization due to a bug in Business Central 28's Base64 decoding (3502)
Bug Fixes
Large files (over approx. 8 MB) became corrupt in SharePoint during journalization – issue introduced with Business Central 28 is now worked around with a fix to Abakion Legal (3502)+
Several customers experienced that files journalized in SharePoint could no longer be opened. The issue affected large files over approx. 8 MB. The file exists in SharePoint but is corrupt and the content is lost — in Outlook the error message "We can't open '...'. It might be because the file is already open, or you don't have permission to open it." could appear when attempting to open the file.
Only customers using SharePoint as their document management system (DMS) and who have been updated to Business Central version 28 were affected.
The cause was a bug introduced with Business Central 28's internal handling of Base64-encoded files. When decoding files over approx. 8 MB, BC28 produced an incorrect result which was subsequently saved to SharePoint. The issue is now worked around by performing the decoding in smaller chunks that are correctly reassembled into the final file.
The fix covers journalization of files from Outlook and from BC.