There is a least one data placeholder that cannot be found in the data source.
This typically appears when updating a data source, rather than starting a new data merge project from scratch. Can also happen through a field name becoming corrupt.A wrong database has been selected as a data source or.The data merge field names that are already placed in the InDesign file can’t be found in the database that has just been linked to. An example is placing a Unicode file as an ASCII file using the “show import options” feature. When attempting to import an Excel file as a data source rather than the CSV or TXT file that needs to be exported first.The data source file you selected either has no records or is not a supported file format. When attempting to import a text file that is either completely blank or has text on the first line only.It often happens because the suffix of the file may be TXT or CSV, but during the saving process was still saved as an Excel file – with the file extension being changed manually instead of using the format dropdown in the save dialog box. Interestingly, the select data source dialog box does let users select any format using the dropdown field located at the bottom center of the dialog.
#Indesign data merge fields scrambling pdf
This can occur when trying to select a PDF or an AI file as a data source, or: Generic extended parser error This can lead to unusual alert dialogs appearing if you’re importing files that weren’t intended to be used as Data Merge databases, such as: Content contains characters which cannot be encoded. #INDESIGN DATA MERGE MULTIPLE RECORDS NOT WORKING PDF# This can occur when attempting to select an HTML file as a data source. See also: Traps when Packaging Data Merge files Other data merge odditiesĬolons used in field names can have some strange behaviors. If there are two or more colons in the field name (neither at the start or end of a field name), a different error occurs: Not well-formed If a colon appears at the start or end (or both) of a field name, the data will import without any issues, but if a colon is within the field, the “Generic extended parser error” occurs. #INDESIGN DATA MERGE MULTIPLE RECORDS NOT WORKING PDF#.#INDESIGN DATA MERGE MULTIPLE RECORDS NOT WORKING HOW TO#.
0 kommentar(er)
