We're sorry AsposeCloud doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.cloud

Getting empty values for all PDF form fields while extracting cloud API https://api.aspose.cloud/v3.0/pdf in C#

Getting empty values for all PDF form fields while extracting cloud API https://api.aspose.cloud/v3.0/pdf in C#

{
“Fields”: {
“List”: [
{
“Name”: “topmostSubform[0].Page1[0].CalendarYear-TypePrint_ReadOrder[0].f1_1[0]”,
“SelectedItems”: [],
“Type”: “Text”,
“Rect”: {
“LLX”: 0.0,
“LLY”: 0.0,
“URX”: 0.0,
“URY”: 0.0
},
“Values”: [
“”
]
]
}
}

@bobbyaspose

The GetFields API method is working fine with my sample PDF document. Please share your sample code along with the input document. It will help us to investigate and address your issue exactly.

f1120s.pdf (655.2 KB)

@tilal.ahmad Thanks for your reply
It is working fine with GetFields API method but i am trying with cloud API
i.e., https://api.aspose.cloud/v3.0/pdf/f1120s.pdf/fields?storage=PDF%20TEST&folder=PDF

image.png (64.5 KB)

image.png (68.1 KB)

@bobbyaspose

Thanks for sharing the input PDF document. I have tested the scenario and noticed the reported issue. So logged a ticket PDFCLOUD-2714 for further investigation and rectification. We will notify you as soon as the issue is resolved.

Thanks @tilal.ahmad for the update you given …

Is there any progress on the issue? Could you able to update me the status about the issue, because it was almost completed week.

@bobbyaspose

I am afraid the issue is still pending for investigation in the queue. We will share our findings/ETA with you as soon as the issue analysis is completed.

Thank you @tilal.ahmad for the reply.

1 Like

@tilal.ahmad is there any update regarding the issue.

@bobbyaspose

The issue investigation is planned for the coming week. Hopefully, we will share the update/ETA with you accordingly.

@tilal.ahmad why ticket PDFCLOUD-2714 was updated as resolved?? when i tried with same API i am still facing same issue. Could you please explain me.

@bobbyaspose

Your issue is resolved but the fix will be available in the upcoming Aspose.PDF Cloud 22.3 release. Hopefully, it will be published at the start of next week.