Home Devices
New Blog Posts: Merging Reports - Part 1 and Part 2

Fail attaching a report to an e-mail body from the preview form

Hello, I am facing a curious problem. From a certain version onwards, our users have been unable to send emails from the screen preview form using the built-in email button function. The email was processed, but there was no attachment. This has only happened occasionally and only for merged reports. My investigation revealed that the problem is related to a 'NewJob' property in the archive report body (as a result of the 'NewFile=True' property in the group header of the original report). This causes individual PDF files to be created in the temporary folder, which the email form cannot find. After spending a day trying to solve this issue (to avoid rewriting the whole mailing mechanism), I found that the only solution is to locate the sequence #06'NewJob'#09 in the data stream and decrease the last byte (#09 to #08, i.e. from vaTrue to vaFalse), which disables this undesirable behaviour for mailing purposes. My question is whether there is a better way to handle this issue. I have also found that reports with this property setting are usually rejected for mailing, but in our case, some merged reports are correct and some are not, so it can't detect them properly.

Comments

  • Hi Igor,

    Thank you for pointing this out. This is a scenario that was not considered when designing the Group.NewFile feature.

    I sent you a patch that solves the problem. After applying the patch, there is no need to manually alter the archive stream.

    Registered customers with an active software subscription can email support@ to receive the patch.
    Best Regards,

    Nico Cizik
    Digital Metaphors
    http://www.digital-metaphors.com
Sign In or Register to comment.