Anklebuster

@PixelEngineer I actually did encounter the Field not found in source early on. I was using a rather long label for single-digit data (Sudoku numbers) so I did what your post suggests to fix it. I haven't tried a TXT source, yet. Have you had any issues with "Data Merge sources need updating" with file types other than XLSX?

Hey PixelEngineer, Thanks for weighing in on this. I'm glad things worked out in your scenario. In my case, I had not made any changes to the workbook recently. Your answer makes me wonder if AP "forgets" to reset its timestamp (I'm assuming that's how it tracks whether a data source has changed.) In other words, if you never edit the workbook after attaching it do the AP document, you will never get the warning; and, if you edit it once, Data Merge never fixes its point of reference.

Hi Dan, Thanks. The two files have been uploaded. It's really no trouble, because the merge works. I look forward to the results of your investigation. Cheers, Mitch

I'm using Affinity Publisher, Windows build 1.10.4.1198. I'm using XLSX as a data source. It hasn't been changed recently. Preflight panel shows the warning and a Fix button, but it doesn't seem to work. I have no idea if my manipulations caused some kind of disconnect. But here are the things I did to create a template: Initially, I began the whole process in my main document, "Puzzles" I created a page (not Master) and used the Data Merge Layout tool to create a "Sudoku" grid After learning more about Data Merge, I decided I should have a separate .AFPUB template I copy/pasted the page from "Puzzles" to a new document I belatedly realized that I should be using a Master page I copy/pasted from the normal page in my new document to Master A This is key: I was concentrating on the Master page and totally forgot to delete the Data merge Layout from the normal page The source field on the normal page was called "Solution", then I changed it to "Puzzle" before I copied it to Master A Meanwhile, I kept tweaking the Master page and renamed the field from "Puzzle" to "N" to help get rid of an Overflowing text frame error After each tweak, I would save the project as a template. Every time I generated the merged document and tried to export it to PDF, Preflight complained about three errors I finally removed the old Data Merge Layout from the normal page. I resized the text frame in the upper cell to handle the Overflowing text error Maybe all that copying, pasting and renaming confused the software. If not, then perhaps the preflight check is not seeing the XLSX as being unchanged.

Hi, Komatös, thanks for sharing this resource! Let me get my popcorn If data merge can't preserve sections, that's okay. I've gotten used to exporting my main document to PDF and would prefer to continue doing so, for file management reasons. My current solution is to create a separate project for the data merge process, save the output as .afpub and then, back in my main document, add pages from file.

I'm new to Affinity Publisher. My current project is a puzzle book. Initially, my workflow was super simple: Create Master Page for new puzzle category Add pages for the new puzzles Apply Master Page to the new pages Type data onto pages or import an image/PDF Export to PDF Today, I learned about Data Merge! That's a game-changer, especially since I figured out how to generate Sudoku pages. My question is whether I should maintain separate .afpub files for each data merge task and use step 4 to Add Pages from File? I tried running the data merge directly in my puzzle book document. When I generated the merge, the new, untitled document correctly recreates all pages; however, it only uses the first and last section names! Thanks for your help!

Howdy! I'm Mitchell Allen (Anklebuster on the web). I'm here to learn! I bought all three personas and am currently focusing on custom puzzle books, using AP.