Known Participant

Question

PDFMaker doesn't recognize [next record] Word mail merge code when merging to PDF

Forum|Forum|5 years ago
May 14, 2020
4 replies
8494 views

A procedure that we've been using for months has suddenly stopped working. Word mail merge to PDF is throwing an error: it's not recognizing <<next record>> as a legit merge code.

We're running Office 365 on Win10, all updates applied.

I'm running a Word mail merge, with data sourced from an Excel worksheet. I'm trying to run the merge directly to PDF, per the "Merge to Adobe PDF" function. (We run this particular merge frequently, but this is the first time it has failed.)

We're getting an Adobe error message that the <<next record>> merge code is not valid. We've deleted the <<next record>> merge code and re-run the merge-to-PDF, but we still get the Adobe error message - even though the code is no longer in the document. We've created a copy of the Merge master .docx - Adobe still throws the error.

We can, however, use the Word merge function to create a new document containing merged records, and that works fine.

Both Word and Adobe have been updated and are current. I also did the Adobe PDF repair procedure suggested in another topic.

Create PDFs

This topic has been closed for replies.

I

IcebearwantsJustice

New Participant

Hi Lee,

I just now ran into the same problem, and I found the solution.
When you want to export to PDF, do not use the "Merge to Adobe PDF" button. Instead use "Finish & Merge" button right next to it, on the left. It will let you save as a PDF at the end, and it works all the same.

I watched this guy on youtube: https://www.youtube.com/watch?v=dGN9LETRiQI

Hope I this helps anyone in the future.

C

CG SF

Participating Frequently

Thank you for posting, I'm having the same very frustrating issue. Can't merge if the "{Next}" tag is in the document.

ls_rbls

Braniac

Not sure what could be the issue.

From what you've shared, I am inclined to think that after an update (or upgrade ) a compatibility issue popped.

I think the current Adobe PDF Maker add-in is not compatible with your Office 365.

You're not the first user that I've tried to help that has confirmed unexpected issues with the MS Word mail merge, specially if it was working before.

According to Adobe Helpx guidance this seems to be a known issue.

See here: https://helpx.adobe.com/acrobat/kb/troubleshoot-acrobat-pdfmaker-problems-office.html#temp_problem

And here is Microsoft guidance on how to also troubleshoot the PDF Maker add-in:

https://docs.microsoft.com/en-us/office/troubleshoot/miscellaneous/incompatibilities-between-office-and-adob

https://docs.microsoft.com/en-us/officeupdates/release-notes-microsoft365-apps

Additional tips:

https://support.office.com/en-us/article/get-the-adobe-acrobat-tab-to-appear-b83cbba3-7bc1-4c75-b8dc-511e07a283f0

ls_rbls

Braniac

Can you please share a screenshot of the error?

LeeTayAuthor

Known Participant

LeeTayAuthor

Known Participant

Hi

I tried at my end, but I couldn't reproduce the third record getting skipped issue. Given the fields that the current Word document has, none of the fields seem to be changing for any of the merged records. Am I missing something?

Thanks

Tanvi

Tanvi - That Word file doesn't work properly with PDFMaker. When I run the merge to PDF - specifying the first 8 records only - I get a message that the Merge was successful, but when it attempts to save the PDF I get this message:

I end up with a PDF with only one page of labels, and only showing the data from one record. (The purpose of the merge is to assign a unique identifier (a serial number, basically) to each label. If you remove the <next record> code, you get two labels with the same identifier. (Look at the serial number underneath the bar code.)

I'll forward you a copy of the (failed) PDF by email.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded