Oracle Analytics and AI

Bar code not scannable

Summary

Bar code not scannable

Content

Hello,

I'm currently working on a report template (rtf file) which is indexed on a field called SHIPMENT_XID. I put in my word document (with the bipublisher local add on for word) the code "<?format-barcode:SHIPMENT_XID;'code128'?>" and uploaded the font code128 onto BI Publisher.

The report comes through with a barcode but the barcode isn't scannable (i've tried with my android app which works for other barcodes). Am I missing something ?

Thanks in advance and sorry if I don't respect some codes here, first time I'm on an Oracle Forum.

Find more posts tagged with

Accepted answers

All comments

Antoine KAIBER

Hi Tim,

Thanks for your help, unfortunately this is not working for me, I had already tried using <?format-barcode:SHIPMENT_XID;'code128a'?> but it doesn't work. When I run the teamplate this is the kind of barcode I get :

Barcode error.png

I just used the template I sent you and changed the code in bardcode field to <?format-barcode:SHIPMENT_XID;'code128a'?>.

Do you remember where you downloaded your Code 128 font ? And did you upload it onto bip ? Under what name ?

timdexter

The BIP Code 128 fonts are available in the BI Publisher installation directory. There is a fonts directory under the Template Builder for Word directory.

Install the Code 128 font into windows and use that in MSWord.

Once on the server, BIP will pick up the font and use it

Tim

Antoine KAIBER

I see there is text required in barcode font, for instance ÌCodeÂÇ,tXXÎ for code 128 :

Cannot scan data printed with a barcode font do you know where I should put this ?

Antoine KAIBER

So I reinstalled BIP for desktop and used the font that is comes with the add-in and my barcode is a bit longer than before in the template and this is what I have :

But when I run the report this is the kind of barcode I get :

So basically it seems like it's the same as before.

timdexter

I think you have mixed up the fonts.

I would

1.remove the fonts from the windows/fonts directory on your local machine

2. Then do the same on the server with the font that you downloaded.

3Now install the BIP delivered font from the Template for Word/fonts directory into the windows/fonts dir

4Use the font in the template

5The command you are using is correct.

<?format-barcode:SHIPMENT_XID;'code128a'?>

code128a refers to the encoding thatyou want applied to your SHIPMENT_XID data not the font you are using.

6 Save and deploy to the server as a new template

Run it and check the result.

Antoine KAIBER

I can't manage to make it work. If the font installed in word is called "Code 128" and in my rtf I put

" <?format-barcode:SHIPMENT_XID;'code128a'?> ", in BIP it should be "Code 128" right ?

timdexter

1. The barcode font being used is the one you downloaded from here:https://www.dafont.com/fr/code-128.font I know its that font because I can reproduce the issue only with that font. Using the BIP code128 barcode, you will not get regular charachers in the barcode.

So, that font is still in your system somewhere and is being used still.

2. I saw that issue with dots when you sent me the template. Im not sure if it was some translation issue with Word when it rendered for me in my English version of Word. I just pasted in the command again and it worked and remained OK.

Tim

Antoine KAIBER

And now when I upload my template onto BIP which the encoded string *<?format-barcode:SHIPMENT_XID;'code128a'?>* (yes I added the " * " this time) I get this kind of barcode in my report :

And when I download my template again it doesn't show the encoded string but this instead :

timdexter

Pleased you have it working :0)

Some points would be greatly appreciated at this point (excuse the pun)

Antoine KAIBER

It works ! Apparently it was in the font mappings properties of the report in BIP :

I had several font families that I had uploaded onto bip then suppressed them (in administration -> font mappings) but they were still in the properties of the report. So I deleted them there aswell and apparently I had to rename the "Default Code 128" into "Code 128" (how the font is named in word) for it to work (I had already dont it in administration -> font mappings) but it hadn't work at the time, for many reasons I guess.