Our Chinese clients started seeing an issue last week with merged document showing Chinese characters as boxes. The first time the document is merged, we see boxes. Sometimes f we merge the document again, the characters are displayed correctly. Can you help us resolve this issue?
EXAMPLE:
Merged document looks like this:
□□□□□□□□□□□□□□□□□□□□□□□□□□□□□□□
We will appreciate it if you please share your sample template/data and output document along with the code. We will look into the issue and guide you.
tilal.ahmad:
I am having a similar issue with a Non-Chinese client. The font for merged information is supposed to be Roboto. When I merge for the first time, the font is not right
EXAMPLE: Invitation Template -Merged with Incorrect Font.PDF (2.5 MB)
It seems you are using some old release, as the output PDF file is showing PDF producer Aspose.Words for .NET 19.3. Can you please confirm you are using Aspose.Words for.NET (on premise API) or Aspose.Words Cloud? You may share the method code where you are calling the Aspose.Words API. It will help us to investigate the issue.
You are using the obsolete API version. The URL is changed to https://api.aspose.cloud since long and please check the latest API Version 4.0. And you can use your custom fonts in the document conversion in the latest API. You just need to upload your fonts to your cloud storage and pass the cloud storage fonts folder path in fontsFolder parameter. It will resolve the issue.
@tilal.ahmad
Thanks so much for the info. We are reviewing the document you provided and the APIs we are using and trying to determine best approach. Can you provide more information about what changed between ver. 1 and 4? This issue just started recently for us and you mentioned that ver 1 was replaced a long time ago. Would it be possible to have a call with our Technical team and someone from Aspose to help guide us through what needs to be done? Also - will you stop supporting 1.1 in the near future?
As stated in the shared blog, V4.0 uses JSON Web Tokens (JWT) for request authentication and has its own API method for storage operations. Please check the following thread to mail merge a Word document with v4.0 in Salesforce. Hopefully, it will help you accomplish the task.
I am afraid we use forums for technical issues. I have shared some details above. However, please feel free to ask any questions in the forum.
We do not support v1.1 anymore, it is obsolete. We are not making any changes or upgrades to it. However, with reference to the above font issue, I am coordinating with our platform team and will share the details.
We are still trouble shooting this issue and still see it happening intermittently. I was able to capture the details in the api usage logs when it happened. The Details in the log show
'Success: Populate document template with data… name ‘ContractNewa0h0l000003DTFBAA4’,folder ‘’,filename ‘’,cleanup ‘ContainingFields,EmptyParagraphs,UnusedFields,UnusedRegions,RemoveTitleRow,RemoveTitleRowInInnerTables’,useWholeParagraphAsRegion ‘True’,withRegions ‘True’,destFileName ‘’
We are sorry for the inconvenience. I am afraid, as I stated above, that now we are only maintaining V4.0 of Aspose.Words Cloud. So we are not making any changes or fixes to older versions. Please migrate to V4.0; it will resolve the issue.
Thanks for the sample code snippet.
When I login to the account and click Files on the left menu, I get the below error ‘Cannot get files for the selected storage’ along with a error on the top right section which I am not able to capture a screenshot. But the message said ‘Error while …’
Could this be causing the issue we are seeing now or could it be any kind of storage issue we are running into causing merge issues. We have now close to 5 clients complaining that the Merge does not happen the first time but does work after 4-5 tries.
No, the formatting issue is related to the above storage error in the aspose.cloud dashboard. Please re login to aspose.cloud, this issue will be resolved.
I am sorry for any confusion. I meant to re-login to view files in the dashboard UI. Otherwise, you do not need to login/re-login to the dashboard to process files in API calls.