How can I pull the ID number of published pdf that uses VC lite not that of the released document

How are you generating and adding the link to the document, for instance is it stored in a property that you add into a Word template in the working copy? And second, at what point and how is the published version converted to a PDF?

I think there should be a way to get the correct link into the published version as long as you update the link in the editable file (e.g. Word) before it is converted to PDF, but the configuration details depend on the answers to the questions above.

Note that in VC Lite terminology, "published" and "released" usually mean the same thing. Working copy is the one that you edit and approve after which a published/released version is created.

The link has been added in the working copy template which reaches 'released' on approval.  Then the document is converted to a pdf in the second workflow and 'published'.

I was wondering if a script or extra state before the conversion 

Below is a snip of the second workflow

If the link is inserted from a property, you may need a small script before the PDF conversion to update the value in the template: UpdateMetadataInFile

However this depends on if the published version has the correct link in its metadata. I still didn't quite understand how the link is formed and inserted into the template.

The link has been inserted into the working document by using the M-Files add-in, then insert property

So then the question is: where would you get the correct link for the published version? Is the link property auto-calculated somehow so that it is correct in the published version's metadata and you just need to get it updated in the template?

So then the question is: where would you get the correct link for the published version? Is the link property auto-calculated somehow so that it is correct in the published version's metadata and you just need to get it updated in the template?

Apologies think I am getting confused or not being very clear. 

The property we are inserting into the document is the document ID and because the working document is a different ID to the published document due to the workflow.  When it publishes it inserts the ID number of the working document not that of the published version and we would like it to display the published document ID number.

Okay sorry, I must have read your message wrong. I thought you had a link to the document (something like https://myvault.cloudvault.m-files.com/xxxxx) in the property. But it's just the document ID. Then I think triggering the UpdateMetadataInFile method in a small script should work, if you are using the built-in ID field in the template.

Much appreciated Joonas.  I have however tried to work out the script for myself but having not had much experience with this can you give me a bit of a steer in the right direction please?

Thanking you in anticipation

I haven't written any scripts myself in a long time, but I think it should be something simple along these lines (not tested). Set it in the Run script section of the workflow state before the PDF conversion.

Vault.ObjectFileOperations.UpdateMetadataInFile ObjVer, -1, False

thank you very much for that Joonas, much appreciated.  I will give that a try