Field values sometimes “disappear” after a pdf is flattened. Don’t know if the values are lost (doubt it), or some sort of sizing/layering issue (most likely), but the end result is the same - nothing on the page where the field were.
using (var pdfForm = new Aspose.Pdf.Facades.Form(source))
Please find "before" and "after" files are attached. Look at the cover/first page.
My system works with pdf files coming from different sources (and versions). Sometimes the aspose flattened results "loses" fields sometimes it doesn't. I'm guessing is a rendering issue, rather than really losing the values, but when it happens, the end result for me is the same.
Currently I may not be able to share the specific API release in which a particular problem related to form field flatten has been fixed, but it appears that fixes in recent release versions have resolved this problem. We encourage you to continue using latest release and in the event of any further query, please feel free to contact.
I am having this same issue with the current release. I have the issue with a 2 page document where values are removed after Aspose.Pdf.Document.Flatten() or Aspose.Pdf.Facades.Form.FlattenAllFields() is called. When using Aspose.PDF v22.1.0 had the issue, upgraded to v22.11.0 and still have the issue. same document.
We have logged another ticket as PDFNET-53190 in our issue tracking system for your case. We will further look into its details and keep you posted with the status of its correction. Please be patient and spare us some time.
The logged ticket has recently been registered in our issue tracking system and it will be investigated and resolved on a first come first serve basis. Your concerns have been recorded and we will surely notify you once there are some updates regarding its resolution. Please be patient and spare us some time.
You can expedite the issue using our paid support channel if this issue is a showstopper for you. In case you already have paid support subscription, you can login there and create a topic with reference to the ticket ID. The issue will be escalated accordingly.