Allow mailmerge using SharePoint (and/orOneDrive) based lists and documents
Allow mailmerge using SharePoint (and/orOneDrive) based lists and documents, as per: https://answers.microsoft.com/en-us/msoffice/forum/msofficesharepoint-msowinother-msoversion_other/word-mail-merge-with-excel-document-in-a/81cd913e-9a57-4bf8-99ca-a766b57b2531
Works fine on a local or mapped drive, and can work if you sync the files to a local drive, but it doesn't work on online files. Surely this should be the way forward?
If you voted for this you should also vote for a request for a more general update to merge which that proposer has said should include more "one-drive and sharepoint" integration. It has around 80 votes and looks like it has a better chance of getting noticed.
I also notice that the thread that is linked to below is locked for new comments after the MS moderator says, paraphrasing, "well it just isn't possible, but here's a complex workaround that no-one but the office geeks will understand" with no explanation as to why it isn't possible. This censorship prevents people like us (ok, we are the office geeks) exposing this for what it is, at least what I think it is, which is a marketing limitation.
Wow I wish I could vote twice for this..... this would be so useful. I like to use word linked to a merge data file in Excel not only as the means of creating and executing a merge to thousands of documents or emails, but also as the record for the merges. In this way a merge of even tens of thousands of letters can be stored and accessed quite economically and efficiently. But, because you can't use a sharepoint source (and we don't have fileshares anymore) it means that only the person that created the merge from their one-drive source, me, can access the merge as a reference record in this way. Of course others could sync the sharepoint file to their one-drive too, but, so far as I know no-one has yet. Most are mystified when word asks them to look for the data source and they give up assuming it is broken. So, we have to use enormous pdf or rtf files (hundreds of mb's) which are plain bl***y awful for this purpose. Don't tell me they are more permanent, they are ones and zeros just the same. I think this limitation is marketing rather than engineering driven. What do others think?
Although the suggested workaround may work (I haven't tried it yet, just about to - https://answers.microsoft.com/en-us/msoffice/forum/all/word-mail-merge-with-excel-document-in-a/81cd913e-9a57-4bf8-99ca-a766b57b2531 ) It seems unsatisfactory that to get this working should need something described as a "workaround" at all. This is Word functionality that has been there for 20 years or more suddenly taken away. If some sync has to be created to make this work then it should do that in the background. As a user, all I should need to have to do is point to the file that has the list I want and then select the list (Excel table). Now that my organisation is being forced to use sharepoint storage and steered away from fileshares more and more gotchas like this are coming to light.
James Bowater commented
I can create a table in an Excel spreadsheet using a data source in SharePoint, but I cannot use a spreadsheet in SharePoint as a data source in Word!!!!
It's been over 15 years since SharePoint lists appeared. With the move to Microsoft 365 Business, SharePoint online and removal of on premise servers, it is even more imperative that SharePoint Lists are added as a data source. As well as mail merge between excel and word when they are stored in document libraries.
Toni Hunter commented
It's all fine to suggest syncing to an Excel document, but if I am half way through a mailmerge and spot that there is a mistake or omission in the data, I have to load sharepoint, change the data, close the Word document, reopen the Excel spreadsheet (because I cannot have it open at the same time as the Word mailmerge document) update the data, save the spreadsheet or wait for it to save, close the sheet, open word reselect the specific records required for the mailmerge and try again. It is stupidly time consuming when I should be able to connect to the data source in the SharePoint list directly!!