cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - Did you get an answer that solved your problem? Please mark it as an Accepted Solution so others with the same problem can find the answer easily. X

PDF form field on title page

jhubackova
11-Garnet

PDF form field on title page

Hello,

I want to use PDF Form Field functionality (in ATX 8.2.2) on the Title Page of the book
(via page region with the Text Generated Content) but in vain.

 

PDF creation is aborted with Error message PDFlib Warnings:
create_field: Invalid field pathname 'textField_0' (name 'textField_0' already exists)

 

The PDF form fields usage inside xml document works correctly according manual: ATX_HOME\samples\APP\PDFFormFields.

 

Is it possible to use this functionality in the Page Layouts (by using Styler only, without editing in ALD) ?

 

Thanks for help

Jana

1 ACCEPTED SOLUTION

Accepted Solutions

Here is solution from PTC Support: 

https://www.ptc.com/en/support/article/CS413728

Cause:

  • Each frame/content stream has its own set of counters, each starting at zero
  • Using the same counter in different streams can therefore result in duplicate field names

Resolution:

  • Use a unique identifier for the field name, such as something based on the location path of the current XML node
//DO NOT USE 
//name: "textField_" + formatting.counters[101]++,

//USE
var fieldName =  "text_field_" +  application.calculateHash(formatting.currentXMLNode.getNodePath(1));
 
 

View solution in original post

3 REPLIES 3

EDIT: or sometime the PDF publishing is finished without error but also WITHOUT Page Region where form field is used.

EDIT 2 🙈:  Form Field of the type "Check Box" works correctly on the Title Page

jhubackova_0-1706882415844.png

 

Here is solution from PTC Support: 

https://www.ptc.com/en/support/article/CS413728

Cause:

  • Each frame/content stream has its own set of counters, each starting at zero
  • Using the same counter in different streams can therefore result in duplicate field names

Resolution:

  • Use a unique identifier for the field name, such as something based on the location path of the current XML node
//DO NOT USE 
//name: "textField_" + formatting.counters[101]++,

//USE
var fieldName =  "text_field_" +  application.calculateHash(formatting.currentXMLNode.getNodePath(1));
 
 
Top Tags