I am running into an issue with a SSRS report and thought I would ask the community about this. We use a software called Troygroup to handle our signatures for check printing.
Essentially what happens is we have an encrypted USB device that gets installed into the printers. This USB has fonts assigned to users names so it will pass PCL esc commands via letters to the printer to decrypt and place the signature on the checks. The issue I am having is once I import the .rdl into SSRS it no longer passes the correct font/font size to the printer so it is not applying the signature. If I print from report builder it works correctly. Also if I print from SSRS portal and export to a word format it works correctly. I believe the issue is when sent directly to the printer via SSRS its passing the info via some sort of HTML translation. I have read some information that we can set fonts with HTML for a report. Another option would be sending the PCL esc sequence directly out of the report. With that said I would think there would be a way to make this work without having to go to those extents. I was hoping someone could help us out with how we could approach this. In crystal reports all we have to do is set an OLE object, is there similar functionally in SSRS to handle this somehow?
I will gladly go into the details with anyone if they have questions on this but for now I will leave at a high level summary.
So I was able to resolve this. After digging around I noticed the below.
1.) This is how the font is getting passed via print jobs or save as PDF
2.) This is how the font looks if added via text in the PDF Editor.
So the issue is the font is not correctly getting embedded when printed to PDF out of Epicor/SSRS.
I believe this is because of the type of Font Embeddabiliity
So the only solution I have been able to get to pass the signature is to print via EMF in Epicor 10 with SSRS reports.
We are experiencing a similar problem with MICR checks for the signature as the font needs to be embedded in the SSRS output but when reviewing the document properties the fonts are missing.
Our current work around was to use the AD User and the Epicor User value to control the suppressing or displaying of the image.
