ImportXml with Checkboxfield value

Hi,

We are using Aspose.pdf for .NET product, version 8.0.0. We purchased the product.

I am having issues with setting the appropriate checkbox subfield based on the value in the xml file. Here is the detail. I have a checkbox field on the pdf file called "CITIZEN_STATUS", it has 4 subfields, only one can be checked (like a radio button.) Each subfield has the following value (or Export Value) respectively:

CITZ, NONC, RES and ALN

The value will come from xml file. The format of the xml is below:

.....

So based on the value above, the appropriate subfield in the checkbox will be checked, in this case, the first one will be checked. But it does not work. It looks like i can only set the value to either "Off" or "Yes" to make the checks appear ot disappear. And when it is "Yes", the last subfield is checked.

We have a lot of checkboxes in various forms that we are populating based on the values set in the xml.

So i wonder if it is even possible to do this using the tool.

Thanks,

Hua

Hi Hua,


Thanks for your inquiry. I’m afraid while testing the scenario with latest version of Aspose.PDF for .NET 8.4, I’m able to notice the checkbox group subfield issue and logged it as PDFNEWNET-35882 for further investigation and resolution. We will notify you via this forum thread as soon as its resolved.

We are sorry for the inconvenience caused.

Best Regards,

Thanks for your reply. I appreciate your response. Please let us know the estimated time for the fix to be made available.

Thanks,

Regards,

Hua

Hi Hua,


As we recently have been able to notice this problem, so we require little time to investigate and figure out the actual cause of this issue. As soon as we have made some further progress towards its resolution, we would be more than happy to update you with the status of correction within this forum thread. Please be patient and spare us little time.

Hi Nayyer,


What is the status on this fix? We are at a critical point in the project to decide the approach because of this bug. Since we have not heard back from you, we are very concerned. Please let us know your estimate.

Thanks,
Regards,
Hua

Hi Hua,


Thanks for your patience.

The development team has been busy resolving other priority issues and I am afraid the earlier reported problem is not yet resolved. Furthermore, please note that you have reported issue under normal/free support forum and as a normal rule of practice, issues are resolved in first come and first serve basis; but the problems logged/reported under Enterprise or Priority support model, have high precedence in terms of resolution, as compare to issues under normal/free support model.

In case you need to have your issue prioritized, you may consider opting for Enterprise or Priority support options. Nonetheless, note that ES/PS support does not guarantee any immediate resolution of issues (because it might be dependent on other issues or feature which needs to be implemented) but under this model, the development team starts investigating the problem on high priority. For further details, please visit Support Options.

We are sorry for this delay and inconvenience.

Hi,


Thanks for your timely response!

We will need to get this issue escalated. With priority support, how soon can you put the fix in? What is the price for this support? We purchased the small business license.

Thanks,
Regards,
Hua

Hi Hua,


As I have stated above, purchasing the Priority Support does not guarantee any immediate resolution of the issue but it increases it’s precedence and development team start investigating the issue on priority basis. Until or unless we encounter any technical limitation or the resolution is dependent upon any missing feature in product, the issue is resolved in timely manner.

For pricing information, please visit Priority Support and Enterprise Support.

Hi Hua,


Thanks for your patience.

I am pleased to share that the issue reported earlier is resolved and its fix will be included in Aspose.Pdf for .NET 8.7.0 which will be published in December-2013. Please be patient and wait for the hotfix.

The issues you have found earlier (filed as PDFNEWNET-35882) have been fixed in Aspose.Pdf for .NET 8.7.0.


This message was posted using Notification2Forum from Downloads module by Aspose Notifier.