Obsolete metadata format, please regenerate

Hi colleagues!
First time I am posting on the forum. Thank you all for the great and valuable work here. It has saved us countless times!

Today I bring a question we couldn’t find a solutions searching the topics.

We’re having trouble seting up a workflow for PDF splitting using metadata. We’ve tried two different scenarios and both result on the following error:

W3001: Error while executing plugin: Obsolete metadata format, please regenerate

Scenario 1:

  • Folder Capture
  • Execute Data Mapping (Output type: Metadata)
  • PDF Splitter (Split method: Split PDF file based on Metadata, Metadata level: Document, Sequencing based on the number of occurences of the level: 200)
  • Send to folder

Scenario 2:

  • Folder Capture
  • Execute Data Mapping (Output type: Metadata)
  • Metadata Sequencer (Metadata level: Document, Sequencing based on the number of occurences of the level: 200)
  • Create PDF (passthrough)
  • Send to folder

Notes:

  • Running PRes Connect Workflow 2021.1.0.2774;
  • Data mapping configuration is absolutely simple: it only defines the record limit;
  • Metadata must be generated via Execute Data Mapping because this will be part of another workflow that needs it. We are just making the parts work separatelly to then join all of them on a single flow. The other parts are working fine, we just couldn’t make the PDF split run;
  • Adding Update Data Records component to workfkow has no effect.

Thanks for any advice.

Hi Renato,

You may want to reconsider the approach here. I do not think that the metadata format generated by the Execute Data Mapping task is compatible with the splitter plugin.

Consider the following plugins:
Create Metadata
Metadata Level Creation
Metadata Fields Management

With those 3 you should be able to define a metadata structure that the splitter can work with.

Alternatively, just split the PDF using Connect instead. There are separation settings in the Output Creation that would allow you to produce multiple files from one input.

Hope this helps!

Hi Stephen!

Thanks a lot for clarifying. We’ve moved to the Connect-based solution and it is working perfectly.

Best regards, Renato

1 Like