November 23, 2010, 03:30 PMact4bsa
I added the command and got the same result. The first file actually has a value that should appear in the report but the file sent is empty. The second file distributed has the record from the first file appearing in the first label of the second file overwritten by the actual first label of the second file distributed.
I am wondering if this problem is similar to the issue with ReportCaster 7.1 not being able to correctly burst a compound report.
November 23, 2010, 03:46 PMPrarie
does this make the whole process stop working or you just getting errors. I have a huge prosess that bursts reports to a distribution file, and I get erors when there is nodata...I still get reports for everyone else.
November 23, 2010, 04:06 PMact4bsa
The process completes successfully with no errors. The ReportCaster log just shows that no report avaiable for an e-mail address based upon the respective burst value in the dynamic address file.
November 23, 2010, 05:15 PMPrarie
I think that's normal behavior.
November 24, 2010, 12:01 PMact4bsa
Prarie. Thanks for your input. I believe I have isolated the cause of the issue.
The issue only appears to occur when the first file to be distributed contains only ONE label. Today is the second time this data scenarion occurred and produced the same issue with the distributed PDF files.
The PDF file bursting is based upon the CLIENT_USERID data values.
CLIENT_USERID = 'A USER A'
CLIENT_USERID = 'A USER B'
CLIENT_USERID = 'A USER C'
CLIENT_USERID = 'A USER D'
The PDF file for the 'A USER A' burst value has only 1 record that meets the record selection criteria for producing a label. All of the following CLIENT_USERID burst values have multiple records that meet the record selection criteria for producing a label.
However, the (first) PDF file distributed for the 'A USER A' burst value is empty and does not contain the label record.
The (second) PDF file distributed for the 'A USER B' burst value contains the label record for the 'A USER A' burst value in the first label position on the page. In that same first label position on the first page in this same PDF file, the label record for the 'A USER B' burst value overwrites the 'A USER A' label record. See PDF files attached to this case for a sample of the label data overwrite.
All subsequent PDF files in the ReportCaster distribution are created with no file or data issue.