Before OneDrive and SharePoint document Libraries, Microsoft fully supported a brilliant system many of us know as OLE -- Object Linking and Embedding. You could select a range of cells or a graph in Excel, then simply Paste Special -> Paste Link or Paste Image (Linked) in Word or PowerPoint, and it would appear exactly as it did in Excel, and any changes to the Excel file would automatically change it in the Word or PowerPoint Document. Brilliant. Beautiful. Nearly perfect. I've used it since the '90s. And this could go just as well in any other direction, such as if you wanted some PPTX slides or DOCX instructions in your Excel file. It also works across many more applications than just the big 3, e.g., Outlook, MS Project, and third-party apps like Corel Draw.
It still works today, but ONLY properly for documents that are only on a local drive. If moved to OneDrive (personal or business), SharePoint, or any other Microsoft-provided online storage system, the links all break following anything that modifies them (sometimes just making a change to the document seems to update them and the links break), because they get assigned GUID-looking http addresses instead of the traditional c:\Users\username\Documents\sourcefile.xlsx for the object, which the hosting document then can no longer resolve. Basically, in moving documents to the cloud, we lose this as one of the key advantages Office has had over competing office suites.
In searching for a solution to this problem, I see plenty of posts asking for solutions, with no good answers. In checking with Copilot, it says it's a known problem with no good solution.
My questions here are:
- MOST IMPORTANT: Is there any work-around? E.g., I've seen hints that if you paste as an image, it may be less likely to break, but I've not gotten than to work. I've seen other posts suggesting locking the objects to prevent linking, but I've not gotten that to work either (and maybe it defeat the whole point of linking and embedding). Perhaps there's a modern alternative to OLE that performs the same function and is intended to work for online documents?
- Does MS realize they broke this and do they have any intent to fix or provide a modern alternative (other than adding Dark Mode to Excel, they seem to be in let-those old Office apps die slowly mode at MS)? Other than Copilot saying it's a known issue, I've not seen it acknowledged publicly by MS.
- I've already reported this in the Feedback Hub. Is there anything else we can do to make sure that MS is at least aware that their recommendations for cloud storage break this core functionality of Office that's been there for decades?