This has come up in past posts, but I didn’t find anything recent. Has Epicor come up with a good native option for cloud customers to use 2D barcodes in SSRS yet? I know 3rd party tools exist but require to run on the report server. Just curious what the most recent update is on this and what opti…

Just a spitball at a way to natively implement now, 2D barcode spec is well documented. You can pass base64 data into ssrs on the fly via CallContextHeader.BpmData, but does have the header size limitations. I don’t remember what formats SSRS rendering engine supports, but a QR code being a black …

It would have to render as a Data Matrix type, not a QR code.

I suppose there would be no reason not to accept an additional input for symbology and various other specifications like guard bar size, etc.

Just curious why the Data Matrix preference? In two unique customer scenarios involving a % sign and a Zebra scanner, I’ve seen issues with a Bartender generated Data Matrix that when switching to QR suddenly worked. No good explanation as to why, but it has skewed my preference since then.

Data Matrix is by default more information dense than a QR, so I would think this may be an artifact of printer DPI/head cleanliness/age?

[image] GabeFranco: header size limitations Evil IO golf solution: A QR/Data Matrix grid boils down to a few dozen bytes worth of points. Send a tiny blob with each bit representing a white/black point, mangle an SSRS table into grid shape, and map specific bits to each cell’s conditional bac…

It is a requirement of some customers.

This seemed like a fun challenge, so, done. [image] [image] [image] Piggybacked a function off zxing, which epicor has included in SaaS on server side assemblies… Use the function in a pre bpm on .SubmitToAgent for your report of choice. Put the base64png output into CallContextBpmData in a st…

Gabe will have you dropping mics till you run out of money to buy another one.

Native 2D Barcodes support yet for Cloud?

Kinetic ERP

GabeFranco (Gabriel Franco) March 19, 2026, 7:18pm 23

Here you go, sir! I said CallContextClientData earlier but it’s CallContextBpmData, that would probably help you find it easier