We have encountered an issue in which all custom report layouts were corrupted after we published an update to one of our extensions. I have attached the errors received for both RDLC and Word report layouts. Unfortunately some of the layouts were not saved locally so we may have to restore a backup of the database on our UAT instance to export all the layouts and reimport them or we may have to recreate them. But my question here goes to cause, what could have possibly happened during the publishing of our extension that could have affected custom report layouts or is this completely unrelated to that event? We did check other blob fields in other tables and we can export those files without issue, so this problem seems to be centered around custom report layouts only. Our product is BC17 on prem, this issue is affecting all multi-tenant instances that received our extension updates, I've tried to create the issue in our UAT database to no avail.
