Expand my Community achievements bar.

SOLVED

How to decode 1D barcode from PDF

Avatar

Former Community Member

I have a PDF that has a single 1D barcode that represents a simple value, ex. "99999-FLM-CC-008217140".  The PDF and barcode were created using a 3rd party tool, not an Adobe product.

Using the default EJB endpoint for a BarcodedFormsService, I created a watched folder to decode this barcode.  The results of the decoding look like this, which doesn't contain the value of the barcode:

<?xml version="1.0" encoding="UTF-8" ?>
- <xb:scanned_image xmlns:xb="http://decoder.barcodedforms.adobe.com/xmlbeans" path="pdf" version="1.0">
- <xb:decode>
<xb:date>2010-04-07T17:05:02.807-04:00</xb:date>
<xb:host_name>xxx99alc01.xxx.org</xb:host_name>
- <xb:status type="success">
<xb:message />
</xb:status>
</xb:decode>
</xb:scanned_image>

What do I need to do to decode the barcode and get a result that has a string that looks like "99999-FLM-CC-008217140"?

Thank you for your help.

Alice

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

Just to update this thread.  LiveCycle ES, and ES2 provide the ability to decode both 2D and 1D barcodes.

You may refer to the documentation for the complete list of supported 1D and 2D barcodes here:http://help.adobe.com/en_US/livecycle/9.0/workbenchHelp/help.htm?content=001611.html

View solution in original post

7 Replies

Avatar

Former Community Member

Alice,

The LiveCycle Barcoded Forms ES decoder supports three 2D barcode symbologies (PDF417, DataMatrix, and QRCode). These are the three symbologies LiveCycle Designer ES supports through the PaperFormsBarcode object. The decoder does not support 1D barcodes.

Steve

Avatar

Former Community Member

Thanks for your response, Steve.  Do you know if there's an Adobe LiveCycle tool that

does support decoding 1D barcodes?

Avatar

Former Community Member

No, unfortunately there is not. The ability to add 1D barcodes to a form in LiveCycle Designer is targeted at workflows where printed or faxed paper forms are processed by third-party scanning solutions (hardware or software).

Steve

Avatar

Correct answer by
Former Community Member

Just to update this thread.  LiveCycle ES, and ES2 provide the ability to decode both 2D and 1D barcodes.

You may refer to the documentation for the complete list of supported 1D and 2D barcodes here:http://help.adobe.com/en_US/livecycle/9.0/workbenchHelp/help.htm?content=001611.html

Avatar

Former Community Member

Based on the information in http://help.adobe.com/en_US/livecycle/9.0/services.pdf, it looks like the ability to decode 1D barcodes is only supported for TIFF images, not PDF files:

"The service also supports the following one-dimensional symbologies supplied as scanned TIFF documents"

"The Barcoded Forms service does not support one-dimensional symbologies in PDF documents."

Avatar

Level 4

If you are still looking to figure out a solution, you could conver the PDF to a TIFF using services in LiveCycle, then use the 1D decoding service on the TIFF without losing data.

Avatar

Former Community Member

Thanks for the suggestion.  However, Lee Sutton (another poster on this topic) helped me with this.  Apparently this statement that I quoted from the Adobe documentation is wrong (and has been reported as a documentation bug): "The Barcoded Forms service does not support one-dimensional symbologies in PDF documents."

In fact, the Decoder tool in Barcoded Forms does support both 1D and 2D barcodes, as Lee said.  However, Decoder only supports printed-then-scanned PDFs.  It doesn’t support barcode PDFs that were generated as electronic files, and were never printed.  In order to decode 1D and 2D barcodes on an electronic PDF, you need to use the Text Extraction Assembler tool, which comes with LiveCycle Output.

The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----