Jump to content

Recommended Posts

Posted

I have a Data Merge Field as the last entry in a file. There are no characters after the last field except the § indicator.

When the Field tag is the last character of a block of text the data will not show when “Preview with record” is checked, but, all other data fields will show the correct data.

As odd as it might seem simply adding a ‘return’ character after the last field to move to the next blank line solves the problem and the merged data appears. Remove the return so only § character follows the last field and all the other merge data will show but not the last field.

I have been able to repeat this time after time. This only happens if a field is the very last entry in a Text Frame so I consider it a bug that should be easy to fix.

MaxClass

OS X Sonoma 14.6.1, Mac Studio M1 Max, 27" Apple Studio Display, 32 GB SSD. Affinity Universal License for 2.0.

Mac User & Programmer since 1985 to date. Author of “SignPost” for vinyl sign cutting.

Posted

Could it be this?

I had a similar problem a long time ago!.. where you just needed an extra field entry to balance the process

 

 

Affinity Version 1 (10.6) Affinity Version 2.6.2  All (Designer | Photo | Publisher)   Beta; 2.6.3.3309
OS:Windows 10 Pro 22H2 OS Build 19045.5371+ Windows Feature Experience Pack 1000.19060.1000.0
Rig:AMD FX 8350 and AMD Radeon (R9 380 Series) Settings Version 21.04.01 
Radeon Settings Version 2020
20.1.03) + Wacom Intuous 4M with driver 6.3.41-1

 

 

Posted

I notice this kind of behaviour when copying text with tabs and carriage returns from a text file and pasting that into a spreadsheet, it doesn't work. The final line needs a carriage return for this to work. I suspect that there is something similar happening here.

Mac Pro (Late 2013) Mac OS 12.7.6 
Affinity Designer 2.6.0 | Affinity Photo 2.6.0 | Affinity Publisher 2.6.0 | Beta versions as they appear.

I have never mastered color management, period, so I cannot help with that.

Posted

Without going too deep, “Old Bruce” said it in a nutshell.

If the last entry in a document is a Merge Field without a “return” following it that last Merge Field will fail to fill in on a “Preview with record”.

You must have a “return” character following it in order for the Merge Data to appear in that field as “Old Bruce” mentioned above.

The only time this happens is if the last Merge Field followed only by the section character “§”.

This should be very easy to duplicate.

It doesn’t so much cause a problem if you add the “return” character so it’s only a partial bug in that sense but should be fixed for the next release.

Great work guys. The Affinity application are amazing.

Max Taylor

OS X Sonoma 14.6.1, Mac Studio M1 Max, 27" Apple Studio Display, 32 GB SSD. Affinity Universal License for 2.0.

Mac User & Programmer since 1985 to date. Author of “SignPost” for vinyl sign cutting.

Posted

Thanks for confirming that for me.

I've created a test document here with a Data Merge .csv file, then within Publisher I have a text frame with multiple data merge fields added - and no return after the last entry.

When using 'Preview with record', all merge fields are populated for me, as expected.

Can you please provide a sample .afpub document & data merge file to the above link that shows this for me?

Many thanks once again :)

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.