Skip to main content
A
AndrewC1264
Known Participant
January 18, 2026
Answered

Data merge hell... has Adobe broken something again [no surprise here]

  • January 18, 2026
  • 2 replies
  • 522 views

Admittedly, it has been some time since I have used data merge, many years ago for a particuarl client, lately not so much. To get up to speed again, searched online for a few answers... most notably answers coming from people struggling to get it to work properly. And finding answers on non-Adobe pages with tips on how things break and what to do. Frustrating.

 

I have a book prohect that has lists at the back of items that are formatted in a table format with about a dozen cells. The cells are not just columns, that would have been easy, can't do it that way. I have two wider cells that are split horizontally to place content - see attached.

 

I got the data merge set up to work - placing the tags from the .csv headers is the easy part.

 

Where things exploded is when I actually merge the document.

 

If I have one table set up and merge the .csv file, even with "multiple records per page" selected as the option to import, I get 495 pages with just one table per page.

 

If I set up a full page of tables, to tell InDesign "hey, this is what I want" then I get 10-12 duplicate records - the same row of data from the .csv file duplicated multiple times. At least it looks more like what I want - 10-12 tables per page, but it's all duplicates, so all useless.

 

Am I missing something or have I found yet another bug that Adobe won't admit to and will take 2-3 years to fix? I'm still waiting for the Command+>< type increase in Illustrator to be restored, such a simple fix, that's been a year at least.

 

Holding breath in anticipation of an answer.

 

Help is much appreciated. Bug fixes are mandatory if this is the case.

Correct answer Colin Flashman

Sorry I'm late to this conversation, but it's been a minute.

About data merging and tables. Eugene has outlined most of what I'd point out. There is one thing that can be done with data merge and tables, but it requires a third party script but it's from a well known InDesign scripter and friend of the community, Loic Aigon. Script is called CSV2tables and can be found here: https://www.ozalto.com/en/solutions-en/downloads/

His site also offers a similar script that will repeat data merge details within the same text frame, better suited for small and easy catalog work that is like a directory. That script is called inlinemerge and is available from the same link.

Lastly, it's been my belief that InDesign's data merge is great for simple tasks, but when trying to place more than one record on a page at once (whether a directory, table or catalog layout) then other solutions may be better. I've written about the pitfalls of this here: https://colecandoo.com/2013/12/28/data-merge-multiple-record-madness/

 

2 replies

Colin Flashman
Community Expert
Colin FlashmanCommunity ExpertCorrect answer
Community Expert
January 20, 2026

Sorry I'm late to this conversation, but it's been a minute.

About data merging and tables. Eugene has outlined most of what I'd point out. There is one thing that can be done with data merge and tables, but it requires a third party script but it's from a well known InDesign scripter and friend of the community, Loic Aigon. Script is called CSV2tables and can be found here: https://www.ozalto.com/en/solutions-en/downloads/

His site also offers a similar script that will repeat data merge details within the same text frame, better suited for small and easy catalog work that is like a directory. That script is called inlinemerge and is available from the same link.

Lastly, it's been my belief that InDesign's data merge is great for simple tasks, but when trying to place more than one record on a page at once (whether a directory, table or catalog layout) then other solutions may be better. I've written about the pitfalls of this here: https://colecandoo.com/2013/12/28/data-merge-multiple-record-madness/

 

If the answer wasn't in my post, perhaps it might be on my blog at colecandoo!
    A
    AndrewC1264Author
    Known Participant
    January 21, 2026

    Colin Flashman sed: Sorry I'm late to this conversation, but it's been a minute.

     

    Sir Colin of the Flashmans.... thank you for showing up, regardless of your lateness... appears I have some learning to do.

     

    Scripts... ok, will see if I can figure this out. I rarely use them but appears I need to fiven the current task at hand.

     

    Much appreciated.

    A
    AndrewC1264Author
    Known Participant
    January 21, 2026

    OK, wow... the inlineMerge.jsxbin script does exactly what is needed, immediately.

     

    I now have 34 fully-formatted pages of expertly-formatted data in the tables I designed and prepared using the data I needed.

     

    Sir Colin of the Flashmans... is there a tip jar handy? 😉

     

    Here are a few pointers when using this script that I have observed....

     

    While yes, you get tables and yes you get multiple tables that fill a page, the script will not use the master text box to flow out with all of the data. You get an error if you highlight a table with the data prompts in the first page master text box...

     

    "The script cannot run. Please select a non anchored text frame and run again."

     

    So if you put the initial table into a standalone text frame and run the script, you get one full page to start with the overflow symbol, and have to manually reflow the rest. Straight-forward text box flowing - Command+Shift to auto flow and you're done.

     

    What you do end up with it separate tables separated by a paragraph return [by default] so technically they are not all formatted as one table, but I get the results I need, a page full of tables with my data within each. No duplicates, no longer the nightmare that was Adobe's default "oh let's give them this they'll be happy" and we were not.

     

    So, as the pages are all individual tables, it also will not allow a table header row which is a bummer but a minor setup requirement - I can simply place the header row on the master page and flow all master text boxes below this.

     

    So, for ease of use and expert formatting,, it is perfect. Data flow took mere seconds for 495 records.

     

    For the table side, completeness, appears to be lacking but can be overcome with some expert formatting. That's on me.

     

    I guess Adobe doesn't reply because it would be something along the lines of "Dear customer we're sorry for the results you blah-blah copy-paste response blah-blah... but we are happy to hear a script by a professional programmer obtained the results you required, we just aren't able to do as much. You're welcome. Adobe."

     

    Thank you very much!

    E
    Community Expert
    Eugene TysonCommunity Expert
    Community Expert
    January 18, 2026

    Good morning - your screenshot is not showing for me.

    You’re not going mad, and you haven’t “broken” Data Merge but you’ve run into limitations and it’s “by design”, not a bug.

     

    What’s going wrong
    Why you get one table per page

    Data Merge treats the entire table as a single object, not the individual cells.

    So when you:

    • place merge fields into cells, and
    • choose Multiple Records per Page,

    InDesign does not see rows or tables as repeatable units.

    Instead:

    • it sees one merged object (your table),
    • and it repeats that entire object per record.
    • That’s why you end up with:
    • 495 pages = 495 records × 1 table per page

    This is expected (unfortunately).

     

    Why you get duplicate records when you pre-build multiple tables

    This one feels like a bug, but again it’s a design limitation.

    When you manually lay out:

    10–12 identical tables on a page, each with the same merge fields,

    Data Merge assumes:

    • “These are 10–12 placeholders for the same record, not 10–12 slots for sequential records.”
    • So during merge:
    • Record 1 fills all tables on page 1
    • Record 2 fills all tables on page 2
    • etc.

    That’s why you see duplicates instead of a flowing list.

    Data Merge has no concept of “next record goes in the next identical structure” unless it’s a single text frame.

     

    The limitation 

    Data Merge only flows records correctly in:

    • a single text frame
    • or a table where each record = one row
    • Once you introduce:
    • complex tables,
    • merged cells,
    • stacked layouts,
    • or multiple repeated tables,

    Data Merge stops being smart.

     

     

    I see 3 options which seem viable and a 4th option that requires some investment

     

    Option 1 - One record = one table row

    If you can restructure even slightly:

    Make each CSV record fill one table row

    Use:

    row height auto-expansion

    cell insets

    paragraph styles

    Even with split/stacked content:

    put the stacked content into separate columns, then visually fake the layout using cell rules and spacing.

    This way Data Merge understands “multiple records per page”.

     

    Option 2: Merge then rebuild layout

    This is common in book production.

    Merge so that you get:

    one table per page

    Then:

    select all tables

    use a script (or manual cut/paste) to flow them into a multi-column frame

    delete excess pages

    It’s ugly, but predictable.

     

    Option 3: Nested tables inside a single text frame

    Create one main table that flows across pages

    Each row contains:

    a nested table with your complex cell structure

    Place merge fields inside the nested table

    Now:

    Data Merge might see “one row per record”

    You still get your complex layout

    This might be the closest you’ll get to “what you actually want” without scripting.

     

    Option 4: Use a script instead of Data Merge

    If this is a serious book project, this is the cleanest approach.

    People use:

    • JavaScript (ExtendScript / UXP)
    • EasyCatalog
    • there might be other catalog plugins

    Scripts can:

    • read CSVs
    • create tables per record
    • flow them properly across pages

    Data Merge simply wasn’t built for this level of layout complexity.

     

     

    Bottom line

    You didn’t miss a checkbox.
    You didn’t mis-set the CSV.
    You didn’t forget some magic option.

    You hit a hard architectural limit of Data Merge.

     

      leo.r
      Community Expert
      leo.rCommunity Expert
      Community Expert
      January 18, 2026
      quote

      Good morning - your screenshot is not showing for me.

      By @Eugene Tyson

       

      The attachment preview functionality has been broken for quite some time (as you know anyway). We can still download and view the attachments by using the download button in the lower right corner of the broken preview window.

      leo.r
      Community Expert
      leo.rCommunity Expert
      Community Expert
      January 18, 2026

      leor_0-1768745593735.png

       

        Terms & ConditionsAccessibility statement
        Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices