What is the notation for accessing the record.id of the current record in Output Creation Settings?
If I can get this as the output name, I can then read it back in and Retrieve the metadata for this further along in my process.
What is the notation for accessing the record.id of the current record in Output Creation Settings?
If I can get this as the output name, I can then read it back in and Retrieve the metadata for this further along in my process.
From what I know this value isn’t available in the output preset.
But instead you could define a metadata field in the job preset which get filled from a data record field (e.g. ${document.metadata.}, where has been defined in the metadata options of the job preset).
Thanks. I am doing that, so I define two metadata tags on the Document level and that’s naming the output files but I was hoping to be able to capture the record_id so that I could read the files back in later and target the _vger_record_id using Retrieve Items.
There may be better ways to do this. In fact, you may want to consider a different way of tagging your data for retrieval in the first place.
Personally, I think I’d define my file name in a field in the data mapper. Then I’d use that field to name my file at output time and I’d always be able to retrieve the record based on the file name, so long as it is unique.
That said, I was able to work out a way to do this without any scripts.
To do exactly this, you’re going to need to re-introduce that number into the record after you’ve run your data mapping. If a value is in your datamapping, you can access it quite easily in your Output settings by using the “Include Meta Data” option in the Job Creation Settings.
More on that here: PlanetPress Connect 1.6.1 User Guide
and here: PlanetPress Connect 1.6.1 User Guide
Now, to get that record ID into your data in the first place, you can either leave an empty field dedicated to it in your data mapping, or you can use the ExtraData field that already exists.
In workflow, you’ll run the data mapping as it is. Your dedicated field for the future record ID will be blank at this time. You’ll then have to use the Metadata Fields Manager to write the value from vger_record_id into the field you created in your data mapper for this purpose. I just used ExtraData, so I wrote the value back to _vger_fld_ExtraData
Next, to push that info back into the connect database, you’ll need to use Update Data Records. You can either do this with the checkmark in Create Print Content, or use the dedicated plugin.
Finally, you’ll run this updated data through the rest of the Connect Document creation process. If you’ve set up your Job Creation and Output creation correctly, they’ll be able to read the value that is now stored in the ExtraData field and use that to name the file in Output Creation
Thank you very much!