Jump to content
You must now use your email address to sign in [click for more info] ×

Problem using Data Merge (Split)


Recommended Posts

I've probably missed a setting but I'm having some difficulty with data merge in a project and I was looking to see if anyone had any suggestions as to where I'm going wrong.

The project is a card game where every 2 pages represents the front and back of a seperate playing card.

My difficulty is that the game has 2 seperate card backs. I have set up 2 master pages for the fronts and backs of the cards and my data source etc.

The "Fronts" master has various fields and images that are layered on top of each other to create a series of cards using different templates and text placement depending on source data and this works great.

The "Backs" master is just an image pointing at a field in the same data source which is a filepath to my cardback images.

I've set the "Fronts" to be applied to pages (every odd page) and the "Backs" to be every even page.

If have 2 actual pages (front and back) in the document the behaviour I'm seeing when I perform a merge is that the Fronts are applied to every page, then the backs seem to over-write every second page so that I get a document that seems to skip every second card.

If I have a single actual page (front) then I get simply the document generated with the card backs missing, even if I apply the backs master page to every even page.

This feels like something to do with the way data merge interacts with master pages and how many pages in the setup document.

Has anyone else experienced anything like this?

Link to comment
Share on other sites

Welcome to the Serif Affinity forums, @Krembler.

I'm not sure exactly how you have that setup, without some screenshots or (even better) a sample document to look at.

I'm also not sure that you can generate two pages from a single Data Merge source. You might need two sources.

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
iPad:  iPad Pro M1, 12.9": iPadOS 17.4.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.4.1

Link to comment
Share on other sites

Hey, thanks for the welcome :)

So what I have is a spreadsheed with a cell that conactenates another cell's contents to a string to create a filename for the card backs: ie.

./templates/"+["cardback1"]+".afdesign"

Which is then a field that the 2nd page full image box (card back page) is pointed at.

so that should be able to exist in the same data source as the card fronts and be referred to in multiple pages surely?

This seems to work fine a I can cycle through the records checking that the correct card back image is being put into the frame in the master file.

The problem is that in the set up , each 2nd card front seems to be being removed and replaced with a card back (see example image).

Do you know of any way to have the merge take into account the assignation of alternating pages properly?

 

I would provide screenshots but I'm getting "-200 cant upload file" errors :(

Link to comment
Share on other sites

Don't think of Fronts and Backs. Think of the actual entire Card. All the information for that Card (the front and back) needs to be on one line in the spreadsheet. You'll have to do a lot of work with designing the spreadsheet.

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

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

Link to comment
Share on other sites

Hey, thanks for the suggestion, but each record already is on a single line in the spreadsheet.

The spreadsheet is actually pretty simple as far as the data ingestion goes.  You could think of the spreadsheet as a simple table like this:

card number | Card name | filepath to front template | filepath to back template

as all the fields for the front of the card are correct (and can be kind of thought of as a single column for all practical purposes) and the back of the card is simply one image box pointing at the correct column (and thus file route) in every record when previewed using the Data Merge control panel.

Unfortunately the fronts and backs of the card have to be on seperate pages as this is a requirement of our printing service.

I got the uploader to work so here is a diagram with screenshots showing the problem.

example.png

Link to comment
Share on other sites

51 minutes ago, Krembler said:

card number | Card name | filepath to front template | filepath to back template

That is only four fields, I would guess you are probably wanting to use more than just items of text and or graphics on the final cards.

Here is a guess about how many columns you would want for use as separate fields in the Spreadsheet;

1027187626_ScreenShot2022-01-02at11_03_45AM.png.bc5d6af917c7bf76563ccc2d102c0d63.png

Some are pics and some are text. You do not want to have just a Picture Frame in the Data Merge Layout. Seeing as this is only going to use one "cell" of the Data Merge Layout, you don't need it at all. You can just place the appropriate fields on Page 1 of the "Master Layout" and not have them inside the Picture Frame which I think you have done, there is a disclosure triangle there.

1015175161_ScreenShot2022-01-02at11_06_26AM.png.7d45022176387252af67d88dfcf8a44f.png

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

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

Link to comment
Share on other sites

Hey, thank you so much! You were absolutely right!

All I needed to do was remove the data layout layer and everything worked perfectly!

Looks like the data merge layer was reading records weirdly.

Getting this to work has taken our game one step further towards being completely off SAAS products :)

Link to comment
Share on other sites

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.