FormEditor#SetSubmitUrl

Aspose.PDF Product Family
1

Hi,

I’m currently evaluating pdf.kit for editing and filling pdf forms. Working with static forms is very easy but i need to handle dynamic forms (created with livecycle 9). I managed to fill Form fields, but I am unable to change the submit url of the submit button.

I tried with different naming conventions (static: Form1[0].Page[0].SubmitButton1[0], dynamic: SubmitButton1) but SetSubmitUrl does nothing (i can pass whatever name i want, it does not even generate an error).

Did I miss something or is this a know limitation? What options do I have?



2

Hi Florian,

Thank you very much for considering Aspose.

Could you please share the input PDF file you’re using at your end? We’ll test the issue at our end and update you accordingly.

We’re sorry for the inconvenience.
Regards,

3

Hi,

I attached a small testcase.

4

Hi Florian,

We’ll look into this issue in detail and update you with the results accordingly.

We’re sorry for the inconvenience and appreciate your patience.
Regards,

5

Hi Florian,

I have looked into this issue, however, I’m afraid, I was unable to get the submit button name. I also tried FormSubmitButtonNames property as shown blow:

string[] submitfields = form.FormSubmitButtonNames;

However, it doesn’t return any submit button names. It looks like Aspose.Pdf.Kit is unable to recognize the submit buttons from this file. Had you been able to get the actual name using Aspose.Pdf.Kit? Which version did you use? I’m using the latest version 5.1.0. If it is not returning the button names at your end too then I’m afraid, we’ll have to look into this first in order to set the submit URL. Please share your thoughts, so we could move forward.

We’re sorry for the inconvenience.
Regards,

6

Actually this is a known issue that’s documented (i think its the same as the FieldNames) :

http://www.aspose.com/documentation/.net-components/aspose.pdf.kit-for-.net/known-issues-in-aspose-pdf-kit-for-net.html

I’m using the newest version available (5.2 atm). I managed to circumvent the problem by saving the pdf form to version 7 (still dynamic forms).

7

Hi Florian,

It is good to know that the workaround helps in your scenario at the moment. However, I have logged a new feature request as PDFKITNET-23917 to support this functionality in future versions. This might take some time. You’ll be notified as soon as this feature is available.

We’re sorry for the inconvenience.
Regards,