I spent too long yesterday adding a QR code to an SSRS report and found too many conflicting instructions. So here’s a brief video on adding a QR code to an SSRS report via a .dll. You can also use web services to generate the image, but I went with the .dll method so I could encode complicated data that couldn’t be easily passed in a url string.
When you enable SSRS for an App, via EAC, the deployment adds a few DLL’s to the ...\ReportServer\bin\ folder, and updates the rssrvpolicy.config file with some entries about DLL’s the Epicor adds.
.
Here’s a sample of what is added to the rssrvpollicy.config file.
<CodeGroup
class="UnionCodeGroup"
version="1"
PermissionSetName="FullTrust"
Name="EpicorCodeGroup"
Description="Epicor Code group for data processing extension">
<IMembershipCondition
version="1"
class="UrlMembershipCondition"
Url="\\usdcadbs00375\C$\Program_Files\Microsoft_SQL_Server\MSRS13.MSSQLSERVER\Reporting_Services\ReportServer\bin\CLSEpicor.dll"_
/>
</CodeGroup>
a similar entry exists in rssrvpolicy.config, for EpiNum2Words.dll
Why doesn’t adding the QR DLL to the bin folder, require an entry in the rssrvpolicy.config file?
That’s a good question. I’ve found google results that say you also have to add it to the GAC. I’ve used the method in my video on 3 different servers and it worked on all of them. I forgot to mention you need to put it in your visual studio directory on your local machine to run report builder locally.
This was extremely useful and works really well in an on-prem environment. We are looking at going to the cloud with Epicor but are still going to need to generate QR codes for our labels. Do you have any suggestions? I’m guessing that Epicor isn’t going to allow the QRCode.dll to be placed on their reporting server. Any suggestions would be appreciated.