Forum Discussion
John_Miller_33501710
Jun 05, 2023Copper Contributor
Mail merge and Excel
I have an Excel sheet data source. When I use it as the source data for mail merge the date format is changed from eg 27/04/2023 to 4/27/2023. I cannot find how to keep the original format - is it in...
NikolinoDE
Jun 06, 2023Platinum Contributor
You can try the following alternative approach:
- In your Excel data source, create a new column next to the date column.
- In the new column, use the formula =TEXT(A1, "dd/MM/yyyy") (assuming the date column is in column A and the first row of data is row 1). This formula will convert the dates to the desired format.
- Copy the formula down to apply it to all the rows containing dates.
- Save and close the Excel file.
Now, when performing the mail merge in Microsoft Word, follow these steps:
- Open your Word document and go to the "Mailings" tab.
- Click on the "Select Recipients" button and choose "Use an Existing List."
- Browse to select your modified Excel data source file (the one with the additional column) and click "Open."
- In the "Mail Merge Recipients" dialog box, make sure that the new column with the formatted dates is recognized correctly.
- Click "OK" to close the "Mail Merge Recipients" dialog box.
- Insert the formatted date field from the new column into your document using the "Insert Merge Field" button in the "Write & Insert Fields" section of the "Mailings" tab.
- Complete the mail merge as usual.
By creating a new column in Excel and using the TEXT function to convert the dates to the desired format, you provide Word with the formatted dates during the mail merge process. This should help retain the correct date format in the merged document.
John_Miller_33501710
Jun 13, 2023Copper Contributor
Thanks. That process you have provided seems to work now.
It is a rigmarole and I do not see why one has to be a programmer to make what on the surface seems like a simple issue - and one that worked fine a little while ago. I assume that the problem has arisen due to a recent update. Maybe this is something that Microsoft can fix?
Thanks for your assistance.
John