Windows: "C:\Users\ username\Desktop\ProfilePics\magazine_staff_pics_andy.jpg".MacOS: /Users/ username/Desktop/ProfilePics/magazine_staff_pics_andy.jpg.For image links, the resource path names can be absolute (below), relative to the data source's or saved document's file location.For JSON files, obtained from web/mobile services or database export, only a single top-level array of objects (and values in those objects) are supported lower level arrays and objects are not supported.The CSV export format is more commonly used, but the TSV format avoids problems when processing data records containing punctuation. For example, a top row of "First name, Last name, email address" would offer the merge fields of First name, Last name and email address in Publisher. For CSV and TSV files, the first line (row) of your data source is used as fields in Publisher the row must contain explicit names to be fields.You can add (or alter) data records to the external data source at any time (even after merging) but don't worry if some records don't contain data as these will be treated as blank fields once merged. Of course, it needs to be populated with data records. The source needs to be available in advance of data merging and have a consistent logical structure that is finalized. Contact lists can be exported from, and other services. ![]() The data source exists outside of Affinity Publisher, typically exported from another app or website.
0 Comments
Leave a Reply. |