DNA Sample Dynamic Form not working properly | Community
Skip to main content
Level 2
July 14, 2025

DNA Sample Dynamic Form not working properly

  • July 14, 2025
  • 1 reply
  • 854 views

Hello all, I work for a company who uses designer to build forms & I am the designer. 

I have a dynamic pdf form that has a qr code that has been created and is printing the user attributes incorrectly. You would think the qr code output would print correctly because the Hierarchy is in order per each field as well as the Collection List. Everything checked is within this list. To make matters even more confusing is that there is a previous file that worked & it's identical to the file that I'm working on: Collection List, Hierarchy, the value of the barcode which is (Automatic Scripting, Delimited format, Pipe, UTF-8 Char. Encoding, etc.) Everything is identical. Why is one field out of order when this barcode is printed?!? 

I don't know what else to do, could someone help.

1 reply

Khushwant_Singh
Adobe Employee
Adobe Employee
July 22, 2025

@tronwi , Can you share both working and non-working files?

TronWiAuthor
Level 2
July 22, 2025

Most certainly... Working file is 02.05.19 & non-working is 07.08.25. Although, I'm not sure how you'll be able to test it? & if you will, i am so interested in the process you'll take to figure this out. I'm pretty stumped here. Much appreciate you even offering to assist.

TronWiAuthor
Level 2
October 14, 2025

Since my last posting, I have made strides by being able to get the barcode (PDF417) to read printing & viewing from Adobe Acrobat Pro.

However, the exception of bringing it into Reader, the Barcode & QR code in certain instances every time you bring it into AEM (6.5) both objects turns gray without making changes to it. In other instances, when you type in a certain field, both objects (Barcode & QR code) turns gray.

Upon researching this issue, I am kind of all over the place and I need help pin pointing the problem, come up with a few or couple of guaranteed doable suggestions for possible execution for the client and move on. 

My initial thought to the prob, how the old form is able to read the barcode but not the new form in Reader is because the newer form was designed in LiveCycle vs AEM. In LiveCycle since 2018, this specific barcode was supported whereas, changing to AEM, it no longer has this support based on how this barcode was built. My other thought was that you would need an additional reader extension (ARES) to be able to read this barcode in reader. 

 

Please could someone set me straight on this seemingly wild goose chase. Is there validity to my argument or am I mis-informed. I am all ears because I am kind of stumped at this point. 

 

There's also more caveat then meets the eye to this prob/decision I must make SOON. 

 

Thank you to all who have at least viewed my anguishing diatribe. 

 

I am close to calling Adobe and asking for support for a possible work around or to work with me for some sort of compromise if any.