Inserting a multi-page PDF into XMpie to be processed through UProduce

878 views
Skip to first unread message

lgr...@apps.cierant.com

unread,
Jan 8, 2016, 5:21:36 PM1/8/16
to XMPie Interest Group
Is there any way to have a multi-page PDF document saved as an asset that can be pulled into an existing file so that it can run as an insert?

I have 3 multi-page PDFs (one is 117pgs and 2 are 147pgs) that need to be tagged and pulled into an existing job based on kit type. I don't know if this is even possible...

I have already set this up so that all 3 PDFs have been saved out as singe pages, then placed into my existing document and each page was tagged with a visibility based on kit type. However, this is causing the job to take hours to process through all of the records...AND... I have just been told that these 3 multi-page PDFs will be updated every month.

My HOPE is that there is some way to save these PDFs as assets that I can check out and check in once a month.

We are processing through UProduce and the final PDF goes directly to print...so the inserted multi-page PDFs would need to run with the entire job. I am NOT concerned about the page numbering within the document. I just need the PDF to be placed in a specific location within the file.

Hopefully this makes sense to someone and there is a workaround.






This message and any attachments are intended solely for the recipient as part of Cierant Corporation business. If you are not the intended recipient, disclosure, copying, use, or distribution of the information included in this message is prohibited -- please immediately and permanently delete this message.

  Cierant is an ISO 27001 certified company.

couch

unread,
Jan 8, 2016, 7:53:49 PM1/8/16
to XMPie Interest Group
It would be useful to know exactly what products you are using (eg is your product created via uStore?) because there could be other options available to you depending on the process or workflow used to create the product.

In general:

1) you can use PDF as an asset in uDirect and uProduce.
2) only the first page of the PDF will be used as the asset because there is no method to select which page is used.
3) by default XMPie production will put the entire PDF into the output file even though only the first page will be used. (This is probably why your production is so slow, and results in large output files.)
4) to avoid the issue with #3, you can split the PDF into separate files for each page and use one or more graphic ADORs to call in the required pages dynamically.
5) in addition to using the technique in #4, you can also turn on "require InDesign rendering" on the advanced tab. This will remove the excess pages from the output (resulting in a smaller output file), but will take additional processing time.

In addition. If you are using uStore, or calling production on uProduce via API, there could be other options for you to merge the PDF into your dynamic print job - eg using FreeFlow Core, or doing something with a 3rd party PDF utility, or programatically with a PDF library. In this case, you are best to scope out the project with XMPie Professional services, or a 3rd party developer.

Tyrone

unread,
Jan 9, 2016, 2:08:50 AM1/9/16
to xmpie...@googlegroups.com

How many record are you processing?

 

It might be better to create a data file of your single pdf name and merge into your data and run the job as single pages for every record. I add an example. This way you run every record as a page first record is details with a blank image background then you switch a layer on for image and this will pull in the image as the nest record and so on until next record with details.

 

Regards,

 

Tyrone O’Brien

Director | Professional services | Multi-Channel Solutions

 

Description: connect_E_logo

 

P: 041 661 4187

E: tyr...@connect1to1.com.au

W: www.connect1to1.com.au

--
You received this message because you are subscribed to the Google Groups "XMPie Interest Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to xmpie-users...@googlegroups.com.
To post to this group, send email to xmpie...@googlegroups.com.
Visit this group at https://groups.google.com/group/xmpie-users.
For more options, visit https://groups.google.com/d/optout.




Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com


image001.jpg
example.xlsx

lgr...@apps.cierant.com

unread,
Jan 11, 2016, 3:28:30 PM1/11/16
to XMPie Interest Group
This job is being processed through UProduce and the record numbers vary from day to day... on a typical day, there are probably @200 records being processed.

This entire job has been a beast from the beginning. Without getting into too much detail, I have had to set up the main file to process out 8 separate "kits" with variable pages, variable data, and pages set up throughout the entire document with visibility tagging to print or not print based on the kit type set up in the csv when processed.

The newest twist to this job was these 3 separate multi-page PDFs that now need to be pulled into the file during processing based on kit-type. For example, if the data in the CSV is calling for kit type F3, version 1 and version 2 of the multi-page PDFs need to be pulled in and processed with the job for final output for the printer.... if for example the data in the csv is calling for kit-type F8, then version 1 and version 3 multi-page PDFs need to be pulled in and processed for print.

Unfortunately, I cannot save each page of the PDF and place into the file for processing (I did this already and it does work, however first issue is that in doing this, the 400+ extra pages along with the visibility tagging required on each page causes the job to run laboriously slowly... hours.... and this is a daily run. ALSO.... These PDFs are being updated once a month, so checking out and then checking in 400+ pages is not reasonable...).

So, my only hope is that I can somehow have the file while processing in UProduce, somehow pull in the correct multi-page PDF(s) so that the entire file will process with the job it has been embedded into.

I hope this makes sense.

Thank you in advance for your help :)

Mark Kuehn

unread,
Jan 11, 2016, 8:03:35 PM1/11/16
to xmpie...@googlegroups.com
I think you might benefit from performing this project in a two step approach.

Step 1: Using XMPie to generate your variable pages, also to insert a single page for each PDF that you need to include with the name of the PDF you need to merge listed on the separator page
Step 2: Using a tool like ABCpdf .NET Professional (about $500), write a small bit of code to go through your XMPie PDFs, parse the name of the file to include off your separator sheet, remove the separator page, and add insert the correct static PDF pages.

This will be much quicker and easy to maintain as your source static PDFs change each month.

-Mark

--

lgr...@apps.cierant.com

unread,
Jan 12, 2016, 3:32:54 PM1/12/16
to XMPie Interest Group
Thank you Mark!! :) I will definitely look into this. I appreciate your help!

Best,

Liz


On Friday, January 8, 2016 at 5:21:36 PM UTC-5, lgr...@apps.cierant.com wrote:

Jonathan Gibson

unread,
Jun 11, 2017, 9:19:21 PM6/11/17
to XMPie Interest Group
My post is a bit out of date I know but you can programmatically insert a page of a PDF using uCreate.

STEP 1
Make sure your data has the appropriate field to pull the correct PDF. Just like you would with any other variable graphic.

STEP 2
Create a 'Graphic' content object pointing at your field in STEP 1 

STEP 3
In Indesign, under the 'File' menu, select 'Place' (or CTRL+D). Navigate to and select one of your PDFs. but before you click 'OPEN' make sure the tick box is turned ON for 'Show Import Options'. Then click 'OPEN'

In the resulting pop-up window select the appropriate page range of the PDF you would like to import on this spread. eg on spread 1 you would probably want to import PDF page range 1-1. Also make sure to select the correct 'crop'. I usually use 'Art', but it does depend on the source PDF. 

Once you've got the settings established click 'OK' and click on the appropriate spread for page range you just selected.

Once the PDF page is placed on the spread, apply the graphic content object created in STEP 2

STEP 4
Rinse and repeat STEP 3 for additional spreads & PDF page ranges

CAVEATS
If you have variable length PDFs (ie diff number of pages per PDF) you would probably need to use a 'dynamic spread visibility' to turn unwanted spreads off. Otherwise you may get blank pages at the end of your output for those shorter PDFs.

This solution may be a bit cumbersome for Igr's problem but thought I would post in case someone else saw some benefit here.

Cheers

J
Reply all
Reply to author
Forward
0 new messages