Thank you!
I opened a case with Epicor on Monday morning about this error, and they just directed me to your post as a “workaround” , while they work on a fix themselves.
Thank you! Thank you! Thank you! You are an Epicor genius!
Thank you @josecgomez from JEM Technical - your fix worked for them as well.
Curious the number of people that have thanked you - makes me wonder how many people applied the fix and did not thank you? And, makes me wonder how many companies need to be strangled before Epicor reacts instead of posting "fixed in 2026.1?
Is there anything we can do other than make tickets “High Priority” and “Escalate”?
DaveO
You saved me so much time with this fix, thank you so much! 
Make an offering to Jobu before submtting them?
Mr. @JMPCONJ - Wow that is an old reference. I had to look it up.
DaveO
THIS is the reason why everyone is completely frustrated with Epicor Support. When essential things are broken in a new release, and everyone is forced into upgrading to the new release, “Fixed in a later version” that isn’t even available yet is an absolute disaster for all involved… and shouldn’t require people scrambling to try and figure out work arounds through customizations.
@josecgomez is that a static QR Code on your SSRS Report or can we add dynamic QR Codes to SSRS Reports? Just curious.
Dynamic
How does one set that up? Is there anything here on how to do that?
I have always used a 3rd party.
However, last year at Insights Alex.A mentioned to me that Epicor has documentation for UCC128, QR, DataMatrix. I honestly have never found it. I will have to keep looking.
DaveO
To me the problem lies with the development and/or QA teams…not so much the frontline support techs that are catching the EpicCare tickets when things go sideways. Code needs thorough testing before release. Can’t put it any simpler than that.