When combining PDFs using Aspose MemoryStream and OptimizedMemoryStream, radio button groups no longer work properly. When the pdf is opened in adobe acrobat and the user selects a radio button that is part of a radio group, all buttons in the group become selected and are unable to be unselected, when the pdf is opened in Adobe Acrobat. When inspecting the fields on the pdf using adobe acrobat, it appears that after these pdfs have been converted to a binary array and added to other pdfs using Aspose MemoryStream, there are duplicate overlapping fields present which causes this issue. These duplicate fields are only present when combined with other pdfs.
When combining PDFs using Aspose’s MemoryStream and OptimizedMemoryStream, you may encounter issues with radio button groups not functioning correctly. This problem often arises from duplicate overlapping fields in the resulting PDF, which can lead to all buttons in a radio group being selected simultaneously.
To resolve this issue, ensure that all form fields have unique names before merging the PDFs. This practice can help prevent conflicts caused by overlapping fields. After merging, verify the properties of the fields to ensure they are configured correctly.
If the issue continues, consider reviewing the Aspose documentation on handling form fields in PDFs for more detailed guidance. Additionally, you may seek assistance in the Aspose community for further support.
Hi, we ensured the form fields had unique names and that did not fix the issue. We did update from Aspose.PDF version 23.12 to 25.10 and that resolved the issue. Are you aware of any bugs that were causing this in older versions that have been patched since 23.12?
Thanks.
It is nice to know that your issue has already been fixed by upgrading to the latest version of the API. Please note that we continuously improve API in every monthly release that can cause many issues to be resolved that were happening in older versions. The support is also provided on the basis of the latest available version. These are the primary reasons that we recommend using the latest version always.
Nevertheless, please keep using our API and feel free to let us know in case you face any issues.