Hey,
how can i ensure the proper sequence when merging two PDFs? Say i get a calendar pdf but with cover and inner pages in separate PDFs, and i always want to have the Cover in the front... Am i missing something there?
Cheers,
Thorsten
merge pdf element
merge pdf element
On one of my flows, I have up to 4 pages of the same job arriving into an "Assemble Job" element. I use the "Rename Job" elements on the pieces coming in to give them a -1,-2,-3 sequence number before they get to "Assemble Job". I have the luxury that they're all arriving from different paths. It works good for my application anyway.
merge pdf element
you imply it's absolutely always using ascending sort order on the job.Name()?
-
- TOP CONTRIBUTOR
- Posts: 628
- Joined: Mon Nov 29, 2010 8:45 pm
- Location: Alpharetta GA USA
- Contact:
merge pdf element
It actually sorts on job.getPath()
merge pdf element
tz8 wrote: you imply it's absolutely always using ascending sort order on the job.Name()?
I'm using jobname before that hyphen for the jobname and they always assemble in the right order whether there is a page coming in for each or not. ex: 1,2,4 or 2,3
dkelly wrote: It actually sorts on job.getPath()
That kinda confuses me. Is it sorting on the incoming paths and not the index number I'm putting on the files? They don't necessarily arrive in order.
I'm using jobname before that hyphen for the jobname and they always assemble in the right order whether there is a page coming in for each or not. ex: 1,2,4 or 2,3
dkelly wrote: It actually sorts on job.getPath()
That kinda confuses me. Is it sorting on the incoming paths and not the index number I'm putting on the files? They don't necessarily arrive in order.
-
- TOP CONTRIBUTOR
- Posts: 628
- Joined: Mon Nov 29, 2010 8:45 pm
- Location: Alpharetta GA USA
- Contact:
merge pdf element
getPath() returns the entire directory and filename including Switch's prefix and the extension. I don't know why it uses getPath() instead of getName() but it does.