Issues with GetGlobalSerno

Tobi Schumann

After a migration from Exstream 16.6.4 to 16.6.70, I havean issue with GetGlobalSerno.

I call GetGlobalSerno and use it in the filename for pdf output.

When I send in a batch file, containing multiple documents and documents with the same customer number should end up in one output file. They are already sorted by customer number in the input, so I just need to keep the same filename until the next customer number.

Log says, that everthing is fine and that there is a different filename for each customer number, but in the output directory, I just get one pdf file containing all documents.

Also when I log the filename variable, that I use in SetDestPath, it looks good.

Anyone ever spot that or might even have a solution?

Thanks in advance.

Vyv

I would check the following:

1. That you are using the correct output connector. Check if you are using JOB or DOCUMENT output modes on your connectors.
2. Check the document trigger is in the correct place in your runtime settings.
3. There is an initial value on the global serial no. (Check it is within your interval too).
4. Do you have a sort definition in runtime set correctly?
5. Are there any other log messages pointing to a different error?

Good luck.

Tobi Schumann

Many thanks for the quick and detailed answer, Vyv.

I will check those points tomorrow.

Tobi Schumann

Hi again,

I checked the project and decided to set up a completely basic dummy project, which reproduces the issue.

XML from resource set triggers the same event four times. All events call the process with connector pdf to write all outputs into one pdf and with pdf2 to create one pdf per document (with serno in the filename). Serno is initialized before job.

Log shows the right filenames in the process calls, but in output, I just get one pdf with the first serno, including all documents.

I attached a dcpackage, export, log, test.xml and my output. For me, that looks like a bug, if I'm not mistaken.

serno.7z

Tobi Schumann

I now tried GetSerno to check, if it is eventually an issue with the connection to DB. Eventhough I tried it with Oracle and Postgres with same result.

Also here I get the same issue.

For me it looks like the Serno functions are not called during PreProc phase.

I solved it for now with a local table und setting up the counter with SetSubst and will open a support ticket.

Vyv

You could log values in the preproc phase like this:

if (preProc()){

preProcLog(0, “Your log message");

}

Maybe that will shed light on it?