# Code128 barcode encoding in reporting module

**URL:** <https://forum.inductiveautomation.com/t/code128-barcode-encoding-in-reporting-module/67504>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [December 12, 2022, 3:07pm UTC](https://forum.inductiveautomation.com/t/code128-barcode-encoding-in-reporting-module/67504 "2022-12-12T15:07:04Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![effeiao](https://avatars.discourse-cdn.com/v4/letter/e/13edae/32.png) [@effeiao](https://forum.inductiveautomation.com/u/effeiao)\
**Post date:** [December 12, 2022, 3:07pm UTC](https://forum.inductiveautomation.com/t/code128-barcode-encoding-in-reporting-module/67504/1 "2022-12-12T15:07:04Z")

</div>

Hello,  
I'm trying to include a code128 barcode in a report, reproducing a barcode provided by our costumer, however it looks different.  
After some attempts I found out that if the datakey is composed by an even number of digits, the barcode pattern created in the reporting module is different with respect to barcode generated using online generators. With an odd number of digits, they are equal.  
My guess is that the encoding in the reporting module is switching between code a/b to code c.

Does anyone know which encoding is used or if I can force to use one?

Thank you in advance for your help.

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [December 13, 2022, 6:18pm UTC](https://forum.inductiveautomation.com/t/code128-barcode-encoding-in-reporting-module/67504/2 "2022-12-13T18:18:28Z")

</div>

You might be able to get somewhere using something like the approach here?

> [@Report Designer GS1-128 Barcodes](https://forum.inductiveautomation.com/t/report-designer-gs1-128-barcodes/60444/2):
>
> You mention both Vision and reporting, so I’m not sure which one you meant, but I believe both are backed by the same open-source library, which has some escape characters mentioned here: The equivalent text representations would be: private static final char ESCAPE\_FNC\_1 = 'ñ'; private static final char ESCAPE\_FNC\_2 = 'ò'; private static final char ESCAPE\_FNC\_3 = 'ó'; private static final char ESCAPE\_FNC\_4 = 'ô'; They appear to be incorrectly reflected in the text output, bu…