Skip to main content
_ross_
Known Participant
April 23, 2025
Answered

Data merge bug - critical

  • April 23, 2025
  • 2 replies
  • 992 views

The new version of InDesign has a terrible bug: when importing a CSV with data merge, it doesn’t import the fields correctly (duplicates images, shifts rows and columns, copies the same cells across entire pages). Every day there’s a new issue with a program we pay a lot of money for, unbelievable...

Correct answer Abhishek Rao

Obviously, I can’t share a screenshot of a client’s data. It’s simply a .csv file with product codes, prices, and descriptions, along with some correctly linked images. I’ve tried splitting the source file to reduce the number of rows (thinking I could import everything in two separate steps), I’ve tried removing the images (thinking I could add them manually later), I’ve tried change the file name, import it again and I even tried converting the file to .txt. Nothing works. I have over 1,000 fields—I can’t import them one by one. I create new price lists every month with different items and have never had problems before. Now every item is duplicated multiple times. I also noticed that the field named “code” changes (the order of the data in the column actually shifts) simply based on the row spacing I set in millimeters during the setup phase. It’s absurd. I will now install some previous versions and try again. I’m wondering how I can verify that 1,000 fields are being imported without errors—shouldn’t that be the very point of using data merge?


Hi @_ross_,

 

Thanks so much for the detailed update, and I completely understand how frustrating this must be.

I tried reproducing the issue on my end using a CSV and a multi-record setup, and it worked as expected on the version 20.3. Since you mentioned you're unable to share the client file (which I totally respect), could you try testing the workflow with a different CSV file or by setting up a new InDesign file from scratch? This can help us isolate whether the issue lies with the file structure or something else entirely.

Also, I agree, it absolutely should not be this difficult when dealing with 1,000+ fields. Data Merge is meant to streamline your workflow, not make it harder. So I’d really like to help get this sorted.

Let me know what you observe after testing with a different file.

 

Looking forward to hearing back from you!

Abhishek

2 replies

Colin Flashman
Community Expert
Community Expert
April 23, 2025

I've been a regular Data Merge user for some time now and can say that I will not use the multiple record feature as it has a lot of 'quirks' to say the least. This is a persistent issue that has been present since I wrote this article some time ago: https://colecandoo.com/2013/12/28/data-merge-multiple-record-madness/

I try to stay in the single record merge format for as long as I can and if I need several records to appear on one page (e.g. catalogue entries) I'll merge with multiple record format to a new InDesign file and then be aware that I have to iron out any faults.

Is there any more information about what is being merged - is it a catalogue, list, school photo array...; sounds like it uses tables (from the opening post, rows and columns are mentioned) so how are the tables used in this instance? 

If the answer wasn't in my post, perhaps it might be on my blog at colecandoo!
_ross_
_ross_Author
Known Participant
April 23, 2025

The problem only occurs with multiple exports (single ones work correctly). How am I supposed to prepare a document with hundreds of fields like this? Everything was working fine until last week, using the same file.

Robert at ID-Tasker
Legend
April 23, 2025

Can you confirm platform, OS and InDesign version? 

 

Have you updated to 20.3 already?

 

You can always easily downgrade to a previous minor or major version.

 

You should disable Auto-Updates.

 

_ross_
_ross_Author
Known Participant
April 23, 2025

OS Sequoia 15.3.2, previous version of inDesign, upated at 20.3 too. Same bug. What version should I downgrade to?