Jump to content

Recommended Posts

  • Staff
Posted

Hi @anto,

Are you using the Data merge field link from Anchor, as described in the thread below? As far as I can tell from a basic sample document, the Anchor name is being pulled through on the generated document from the data source.

 

If it's not or if I have misinterpreted it may be helpful to see a sample doc and data source. 🙂

Posted
20 minutes ago, NathanC said:

Hi @anto,

Are you using the Data merge field link from Anchor, as described in the thread below? As far as I can tell from a basic sample document, the Anchor name is being pulled through on the generated document from the data source.

 

If it's not or if I have misinterpreted it may be helpful to see a sample doc and data source. 🙂

Thanks for the link, but I don't understand how to do it. It's very confusing. I have all the names anchored.  I don't need hyperlinks. Is there a video tutorial somewhere?

2025-01-29135708.png.65d6fd0625b831da3acac59d83f02664.png

  • Staff
Posted

Unfortunately there isn't an updated Data merge tutorial, which is inclusive of the newer functions added in V2, but it's something that I'll raise with the team.

I've created a very basic two page sample template which uses the Anchor link concerning the example data set used in the original post. <Record Anchor> uses the first field records A1 to A8 on Page 1, and <Link To Anchor> is the second field on Page 2 which has A1 to A8 but in a different order.

I've added an Anchor to Page 2, enabled 'From Data Merge' and set it to use the <Link to Anchor> data merge field, this will just use the default 'Anchor 1' name in the merge template since i've not changed it.

Screenshot 2025-01-29 at 13.18.00.png

I then highlighted the <Record Anchor> Field on page 1 inserted a hyperlink, Set it to 'Anchor 1' and set it to link to the <Link to Anchor> field via 'From Data Merge' again. 

Screenshot 2025-01-29 at 13.27.01.png

 

When I generate the merge, this will respectively hyperlink <Record Anchor> A1 to <Link to Anchor> A5, A2 to A6, A3 to A7 etc. and will also name the respective anchors in the anchors panel accordingly. Comparatively, If I were to just link to an Anchor which doesn't use the 'From Data' data merge, every record would just link back to A5 as it's the first record. The feature essentially allows you to cross-reference data merge results.

I've attached the documents (.ZIP file) below for reference; I'm not sure if it would work for your specific document/workflow but thought It would be worth referencing that it can pull the anchor names (and therefore export to PDF bookmarks) from the dataset.

 

Data merge Anchor field link.zip

Posted
6 minutes ago, NathanC said:

Try the same workflow in 2.5.7 release, looks like a possible bug in the beta.

Thanks. In 2.5.7 it works. 

2025-01-29160306.png.66e28a8ad4451f6a329817fc94c5183c.png

Posted

Will this be fixed in 2.6, since the bug belongs to the beta version?

Do I need to move the topic to the beta forum?

  • Staff
Posted

No need to log in to the beta section for this issue, since I've already put the work into re-creating the issue I've logged it internally as a regression in the 2.6 beta. 🙂

Posted

Hi @anto,

On 1/29/2025 at 3:45 PM, anto said:

Will this be fixed in 2.6, since the bug belongs to the beta version?

The workaround in 2.6 is to leave the Anchor name blank when inserting your Anchor...

Affinity Designer 2.5.7 | Affinity Photo 2.5.7 | Affinity Publisher 2.5.7
Affinity Designer Beta 2.6.0.3125 | Affinity Photo Beta 2.6.0.3125 | Affinity Publisher Beta 2.6.0.3125

MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

Posted
39 minutes ago, anto said:

This does not work

Strange, it's working here on both Windows and Mac...

Affinity Designer 2.5.7 | Affinity Photo 2.5.7 | Affinity Publisher 2.5.7
Affinity Designer Beta 2.6.0.3125 | Affinity Photo Beta 2.6.0.3125 | Affinity Publisher Beta 2.6.0.3125

MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

  • Staff
Posted

The issue "Data Merge - Creating Anchors from Data Merge fields fails to pull Anchor name from merged result" (REF: AF-5733) has been fixed by the developers in the latest beta build (2.6.0.3106). The fix is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Affinity Info Bot to notify us.

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.