SharePoint Taxonomy Field Conversion

Aspose.Words Product Family
1

Hi Guys, I have a small but annoying issue when converting a Word document.
If the source Word document contains a Word Quick Part which references a SharePoint taxonomy field and which pulls in data from the SharePoint Managed Metadata Service (MMS) then on the converted document (PDF, XPS etc.) the field gets appended with GUID text value which I can only assume is the term store ID.

So for example, if the Word document has an MMS Quick Part that shows as ‘Company X’ in Word when converted document it is displayed as Company X9c0e8e5-2116-42cf-8832-75a3d2a01e1d.

Is there a fix or workaround for this?

2

Hi Colin,


Thanks for your inquiry. Could you please attach your input Word document and output PDF file showing the undesired behavior here for testing? Which Aspose.Words component are you using (Aspose.Words for .NET or Aspose.Words for SharePoint)? I will investigate the issue on my side and provide you more information.

Best regards,

3

Hi Awais,



Thanks for the quick response. I have attached two sample file as requested but bear in mind that the issue is to do with data coming from a SharePoint MMS field through a Quick Part and of course you will not have access to my MMS term store.



I am using Aspose.Words for .NET.



Kind Regards

Colin

4

Hi Colin,


Thanks for the additional information. While using the latest version of Aspose.Words i.e. 13.11.0, I managed to reproduce this issue on my side. I have logged this issue in our bug tracking system. The ID of this issue is WORDSNET-9398. Your request has also been linked to this issue and you will be notified as soon as it is resolved. Sorry for the inconvenience.

Best regards,
5

Hi Awais,

Thanks for the update and for the prompt response - standing by.

Kind Regards
Colin

6
Hi,

Sure, we will keep you informed of the status of this issue and let you know via this thread once it is resolved.

Best regards,
7

Hi Guys,

Do you have any idea when we might expect a fix for this?

8

Hi Colin,


Thanks for your inquiry. Unfortunately, this issue is not resolved yet. I have verified the status of this issue from our issue tracking system and regret to share with you that the implementation of this issue has been postponed till a later date. We will be sure to inform you via this thread as soon as it is resolved. We apologize for your inconvenience.

Best regards,
9

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

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