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

Free Support Forum - aspose.com

Support for DISPLAYBARCODE merge field?

Aspose.Words Product Family
#1

Hi,

We need to decorate some of our documents with QR codes. I want to leave that choice entirely up to the author of the document, so the ideal solution would be to use the DISPLAYBARCODE merge field. But when I test this, it doesn’t seem to be supported by aspose.

Am I doing something wrong, or are you indeed not supporting this? If not, do you have plans to support it?

Regards,

Morten

#2

Hi Morten,

Thanks for your inquiry. Could you please attach your template document containing ‘DISPLAYBARCODE merge field’ here for testing? We will investigate the issue on our end and provide you more information.

Best regards,

#3

Thank you for your response. I have attached a template with DISPLAYBARCODE merge fields. One field uses static data to create a QR code. The other field uses a mergefield (First_Name) to create a QR code.

Morten

#4

Hi Morten,

Thanks for your inquiry. We are in communication with our development team and will get back to you soon.

Best regards,

#5

Hi Morten,

Thanks for being patient. We have logged your requirement in our issue tracking system as WORDSNET-10944. We will further look into the details of this requirement and keep you updated on the status of this issue. We apologize for your inconvenience.

Best regards,

#6

Hi Morten,

Thanks for being patient. Please note that there is no “DISPLAYBARCODE merge field”. The DISPLAYBARCODE field has following field code schema:
https://docs.microsoft.com/en-us/openspecs/office_standards/ms-oi29500/cbc893c0-9683-416d-84c6-407a92451c19

The DISPLAYBARCODE field has no separator and MS Word layout engine render bar code. So, Aspose.Words supports described scenario with saving result to docx format.

To support this field type completely we need to add new field type and field class with field code annotation and implement generation and rendering of bar code in rendered documents.

However, before we proceed further and implement your request, could you please let us know if you also want to save the document in some rendered format like PDF/XPS/Images? Can you please describe your scenario/usecase in detail? Thanks for your cooperation.

Best regards,

#7

Hi and thank you very much for the updates.

In my specific scenario, we have some templates in .docx format where we would like to include DISPLAYBARCODE to include a small QR code with the document reference so that printed documents can be scanned later and included in our archive. The QR code would greatly simplify the scanning and registration process of these documents. We also want to be able to save the merged document directly as PDF, including the QR code.

Thanks

#8

Hi Morten,

Thanks for the additional information. We will keep you informed of any further developments and let you know once this issue is resolved.

Best regards,

#9

Hi,

Is there any news on this yet?

Thanks,

Morten

#10

Hi Morten,

Thanks for your inquiry. Unfortunately, your issue is not resolved yet. We have asked the ETA of this issue from our development team and will update you as soon as any estimates are available. We apologize for your inconvenience.

Best regards,

#11

Hello again

We are getting very close to needing to implement our scenario. If we can’t have full support for generating the barcode field, is it possible to at least get a new callback for this particular field to make it easy to develop templates with barcodes in them and easy (easier) to handle the merging?

Thanks

Morten

#12

Hi Morten,

Thanks for your inquiry.

Regarding WORDSNET-10944, our development team has planned to include the fix to this issue in 15.3.0 - Mar 2015 release of Aspose.Words. If everything goes by plan, we are very hopeful to include the fix to your issue in Aspose.Words’ March 2015 release. We will inform you via this thread as soon as a release containing the fix to your issue is published. We apologize for your inconvenience.

Best regards,

#13

The issues you have found earlier (filed as WORDSNET-10944) have been fixed in this .NET update and this Java update.

This message was posted using Notification2Forum from Downloads module by aspose.notifier.
#14

Hi again,

Do you also have support for the MERGEBARCODE field? It is the same as DISPLAYBARCODE, only it uses a merge field instead of a fixed value.

Thanks,

Morten

#15

Hi Morten,

Thanks for your inquiry.

Unfortunately, currently Aspose.Words doesn’t support MERGEBARCODE field. However, we can add the support for it. We have logged a new feature request in our issue tracking system. The ID of this issue is WORDSNET-11981. Our product team will further look into the details of this problem and we will keep you updated on the status of correction. We apologize for any inconvenience.

Secondly, we request you please elaborate your use-case of MERGEBARCODE in detail. This will definitely help us better understand your requirement.

Best regards,

#16

The issues you have found earlier (filed as WORDSNET-11981) have been fixed in this .NET update and this Java update.

This message was posted using Notification2Forum from Downloads module by aspose.notifier.
(4)