not found in source.),will populate below this warning and identify the name of fields that are not matching with your source database.Ĭlicking the "Fix" button will not magically update a changed field. It seems that clicking "Fix" will invoke a check to see if there are any fixes that need to be made from changes in an updated and "Saved" database source.Īfter clicking "Fix", If it finds that a field has changed, a Preflight error description (Field. The following will only cover Data Merge errors that I've come across and how I approach them.įor "Data Merge Sources need updating", this is how I'm using the Fix button for now. Image snapshot source: Affinity Publisher Help Data Merge xlsx document open "live" while I was working on it on my own version of a Data Merge document. Please note that this was an observation above is based on a scenario that I created from my end having the. Generally when working with databases, the source should be saved first before updating your document. Preflight is smart and noticed the change live, but the "Fix" and "Update" buttons will not work until you first save the. xlsx document first before clicking "Fix" button or "Update" button since it is pulling this data from another source's saved state. The way to prevent this from happening is to make sure that you click "Save" in your. When I clicked the "Update" button in the Data Merge dialog box, nothing happened. When I clicked the "Fix" button nothing happened. xlsx document and noticed preflight warning me that "Data Merge sources need updating" in the preflight. Verifying the preview text, I then went to change the record in the. I used the Data Merge Layout tool to create the box where the data would be imported from the records in the. Hello, I created my own Data Merge example and simulated the problem and was able to re-create this scenario: Once uploaded, please reply here to let me know. afpub file and the data merge document, so that I can investigate this further for you.Ĭan you please upload this to the below link for me: Hi to hear you're having trouble! I'd like to request a copy of your. If not, then perhaps the preflight check is not seeing the XLSX as being unchanged. Maybe all that copying, pasting and renaming confused the software. I resized the text frame in the upper cell to handle the Overflowing text error I finally removed the old Data Merge Layout from the normal page. 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Īfter each tweak, I would save the project as a template.Įvery time I generated the merged document and tried to export it to PDF, Preflight complained about three errors The source field on the normal page was called "Solution", then I changed it to "Puzzle" before I copied it 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 I copy/pasted from the normal page in my new document to Master A I belatedly realized that I should be using a Master page I copy/pasted the page from "Puzzles" to a new document I created a page (not Master) and used the Data Merge Layout tool to create a "Sudoku" gridĪfter learning more about Data Merge, I decided I should have a separate. Initially, I began the whole process in my main document, "Puzzles" But here are the things I did to create a template: I have no idea if my manipulations caused some kind of disconnect. Preflight panel shows the warning and a Fix button, but it doesn't seem to work. I'm using Affinity Publisher, Windows build 1.
0 Comments
Leave a Reply. |