Skip to main content
Inspiring
August 3, 2022
Question

"Widget" annotation not nested inside a "Form" structure element PDF

  • August 3, 2022
  • 1 reply
  • 12712 views

 

Hello all!

Reposting with different title hoping to get help. Cannot figure this out!

In the attached document I get an error in Pac3 for a Save and Reset button on page 1 of this document.

 

The error is: "Widget" annotation not nested inside a "Form" structure element PDF

 

 

 

 

Can someone please tell me how to fix this?

I've tried:

  • Deleting the tags and the buttons and putting them back
  • Deleting the buttons (this makes the ones on page 2 then have the same error); when I re-add in the buttons the error moves back to page 1 buttons
  • Having a colleague do the same things.
  • Using Foxit instead of Adobe (which oddly is the only way I can select options on the "Reset" button to select what fields I want to reset).
  • I don't want to restart just to have the same issue at the end.

 

PLEASE HELP!!!!!

Thank you anyone who can help!

Cyndy

This topic has been closed for replies.

1 reply

ls_rbls
Community Expert
August 3, 2022

Can you confirm what was the source document that produced this PDF?

 

Also, does the save button using any type of document-level script or an Acrobat built-in feature?

 

You also mentioned that on Foxit you're able to use a reset button, but your screenshot shows a button labeled as "Save".

 

Do all the button widgets assigned a unique field name in that PDF?

CyndyB836Author
Inspiring
August 23, 2022

Hi there!!

 

The source document was a Word doc. The Save and Reset buttons were added in Foxit using the push button feature.

 

There is no script atrtached both buttons use the Adobe built-in features.

 

Yes all the buttons have different names (usually the same name with a different number)

What I was speaking about in terms of the Reset button in Foxit is the popup in the screenshot below. In Foxit I am capable of selecting those boxes were as in Adobe I cannot.

 

Thank you for any help you can provide!

Cyndy

 

ls_rbls
Community Expert
August 24, 2022

Based on the screenshot provided, I think the problem with Acrobat is direactly related to the field objects naming conventions that were used with Foxt's JavaScript for Java, and how  the Adobe Acrobat's JavaScript core interpreter fails to interpret such field names. But this is my guess only... I may be entirely wrong.

 

But for the sake of proving my assumption, for example, I see a few field names in that list that have special characters combined with empty blank spaces.

 

Since the PDF field objects were originally created with Foxit PDF, I would assume that the Adobe Acrobat Core API JavaScript interpreter is having issues with field names and how they interact with other elements that are supposed to work well with Foxit PDF's own JavaScript for  Core API in C++, C#, and Java implementation, for example.

 

If the fields in that PDF have field calculations and is throwing errors, a quick fix would be to delete or edit  those fields with Adobe Acrobat and also rename the fields... IMHO.