• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

Best way to incorporate a master list of codes into many different ind/indt files

New Here ,
Nov 20, 2023 Nov 20, 2023

Copy link to clipboard

Copied

I work in a highly regulated field with lots of beaurocracy. Each year, we submit templates to a regulatory body and receive an "approval code" for that year. We update these into our .indt file so that all net new work will have these codes. In this case, I have an .indt file with 8 parent pages of different fax templates, each with their own unique code (8 codes total).

 

Another consideration is that client work created from the now "old" template file needs to be updated as re-prints come up. It's on our very small team to catch this throughout the year (among a million other regulatory things). 

 

My current proccess is to manually copy and paste the codes from a list my co-worker makes. Not great.

 

I explored data merge as an option, but seems more tedious in some ways (manually adding placeholders to all client work, needing to click "preview" everytime i open the .indt file to see the codes). Is there a better way to have a "master list" of codes that can be easily implemented? Is there a script that can help?

 

Thanks! 

TOPICS
How to

Views

60

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Nov 20, 2023 Nov 20, 2023

Copy link to clipboard

Copied

LATEST

The simple solution, to me, seems to be maintaining this list of codes as an independent INDD document, and then placing that document within all the others that contain the information. Updating that doc will update the pages in all the others.

 

You could also do this with a placed PDF — that is, export the codes source doc to PDF and place that instead — which would provide a layer of insulation against unintended changes. (An accidental or pending change to the source doc would only propagate once you exported a new PDF.)

 

Does that sound like a solution?


┋┊ InDesign to Kindle (& EPUB): A Professional Guide, v3.0 ┊ (Amazon) ┊┋

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines