I am trying to split a PDF containing many records into individual PDFs of one record each, based on the boundaries defined in my DataMapper config. I feel like I know what to do, but I am getting the above error in Workflow when trying to execute the Create Job plugin.
My Job Creation Preset defines the appropriate fields
All you need to do is check “Separations” in your Output Preset, and tell it to separate by “Document”.
If you want to name each PDF using values from metadata/data mapping, you’re on the right track. The Output Preset can use the metadata variables you created in your Job Preset.
Thank you for the reply. The error I was getting was resolved by putting the Create Print Content tool BEFORE the Create Job tool in my workflow process.
You can use the All in One step, which will enforce the proper sequence of Connect Steps. If you use the individual Connect plugins, you have to run them in the right order: Data Map, Create Print Content, Create Job, Create Output.
In regard to the error you’re getting now: I wonder if you’re running a “newer” or “older” version of Connect vs. Workflow. My speculation is that one of them supports passing parameters into Output Presets, but one of them doesn’t. Make sure that your versions of Connect Design and Connect Workflow match.
Thank you for the replies. I have found the solution.
While updating to the latest versions of both Designer and Workflow was necessary, the real issue was right in front of my face the whole time. Knowledge base says this error is likely caused by a blank page in the PDF, which I assumed meant the source PDF. My PDF had no blank pages.
But, I screwed up the boundaries in the Datamapper, resulting in 1 record having an extra page with no data fields present. Since one of the data fields was supposed to be the filename of the separated PDF files, the above error resulted. Blank page in the PDF!
I have been able to move forward with this project but I am far from finished. I appreciate the activity on this forum, as it will be a valuable resource as I delve deeper into Connect.
I am bumping this topic. I thought I had this issue resolved, but this error has returned in a new process that is basically a carbon copy of the previous.
I need to know what this error means so I can fix it.
Knowledge base has this to say:
ERROR W4206
Summary:
Metadata does not contain valid Content Set Item Collection
Problem description:
The metadata provided to the plugin did not contain the proper nodes
Cause:
All Group nodes must have the ContentSetID property to use a Job Preset file
Suggested solution(s):
The ActionCreateContentSet plugin must be run before the ActionCreateJob plugin
I am curious what the ActionCreateContentSet plugin is, as I do not have access to it in the Workflow Config.
Any further insight would be appreciated. Separating a PDF file by record seem to be simple task for Connect. Why is it giving me so much trouble?
I assume ActionCreateContentSet is Create Print Content, since that plugin literally creates a Content Set. The output of Create Print Content is the input for Create Job.
If you double-checked that these plugins are in the right order now, I’m not sure what might be going on.
This process does not have any content creation (print/web/email). Its only function is to separate a PDF file containing many utilities statements by record. It is a near duplicate of a previous process, which works as intended.
The number of possible options is so small, I do not know what is different. I am sure it relates to using a data field as filenames for the split PDF files, as the error occurs in the Job Preset.
