This has come up a few times as of late so I thought I would address it.
You can consider this Part 2 of the article of the other day where I show you how to separate out the separate letters or documents of a merge output file.
Current Scenario: 10 page Agreement with a live multilevel outline and merge field codes. The complaint on three occasions was that when the second agreement was generated and so forth, the multilevel outlining continued to pile up instead of restarting:
1. The main document (in this case an Agreement), should be viewed as a static file not a dynamic file. By dynamic, I mean a document with a live multilevel outline.
2. While you may have formatted the document using multi-level outlining, you don't need the live multi-level outline to run the merge. Once the document is done, you should make a copy of the file.
3. In the newly copied file, strip off the multi-level outline so that it is now just plain text but the numbering is still in place as originally formatted and preserved in the manner you intended.
4. To strip the multi-level attribute off the document thus producing plain text, highlight the file (Control A) and do Control-Shift-F9. The document will now be "Static".
5. Now place in your Merge Field Codes and you are ready to go.
6. Now your Agreement is ready for the merge and as each Agreement is generated, the numbering should be perfect since the multi-level outline is no longer an issue.
Next time you have a merge that involves a multi-level outline, try this method first for a smooth process.
No comments:
Post a Comment