Goal: My intent is to help a user outside of my organization upload any multipage PDF that has multiple fillable fields inside of PDF document where some of the fields were unknowingly tagged with the same name. If the users were internal we could request that they tag the PDF with unique names but we don't have that luxury in this case. We need to find and fix issues using iTextSharp without bothering the user and/or partially detecting their tagged fields.
Current State: What happens today when using iTextSharp is that only distinctly-named fields are detected. Fields that are using identical names as others are "ignored" for all intents and purposes.
Example: I have a PDF with three tagged fields named as follows: One, One, Three. When I run the PDF through iTextSharp, it is only picking up two AcroFields (One and Three). The second field named "One" is not in the AcroFields collection. What is interesting is that all three fields ARE in the AcroForm.Fields collection but has limited MetaData information about each field. The information I can access within the AcroForm.Fields items are "/DA, /DR, /FT, and /T". None of these have what I am looking for (below).
Question: I have code to add a new field to the AcroFields collection and it is working but I am missing information about the second "One" field and need to pull key information such as height, width, page number, x, y coords of where that field was. My plan is to dynamically add the missing AcroFields back into the document such that the textbox is positioned correctly and is the appropriate size when the user sees it later. The end result would be that the user sees no visual difference, isn't notified of issues, and is fully corrected by implementation I am working on.
Thoughts or suggestions?
Of course, if I have missed anything in this question or if the approach is wrong please advise.
