Hi,
My company has an application using syncfusion to read docx files, almost files work fine. But there is a docx file which contains chart, syncfusion can't read it. If I remove the chart in this docx file, syncfusion will work fine.
Note: I updated the newest version 20.1.0.52. If I use the older version, it will work fine.
Please provide us with a quick fix for this issue.
Thanks,
Tuong.
Attachment: The issue file contain chart
System.NullReferenceException:
at Syncfusion.OfficeChart.Implementation.NameImpl.get_Columns (Syncfusion.OfficeChart.Portable, Version=20.1200.0.52, Culture=neutral, PublicKeyToken=3d67ed1f87d44c89)
at Syncfusion.OfficeChart.Implementation.Charts.ChartSerieImpl.set_CategoryLabelsIRange (Syncfusion.OfficeChart.Portable, Version=20.1200.0.52, Culture=neutral, PublicKeyToken=3d67ed1f87d44c89)
at Syncfusion.OfficeChart.Implementation.Charts.ChartSerieImpl.Clone (Syncfusion.OfficeChart.Portable, Version=20.1200.0.52, Culture=neutral, PublicKeyToken=3d67ed1f87d44c89)
at Syncfusion.OfficeChart.Implementation.Charts.ChartSeriesCollection.Clone (Syncfusion.OfficeChart.Portable, Version=20.1200.0.52, Culture=neutral, PublicKeyToken=3d67ed1f87d44c89)
at Syncfusion.OfficeChart.Implementation.Charts.ChartImpl.Clone (Syncfusion.OfficeChart.Portable, Version=20.1200.0.52, Culture=neutral, PublicKeyToken=3d67ed1f87d44c89)
at Syncfusion.OfficeChart.Implementation.Charts.ChartImpl.Clone (Syncfusion.OfficeChart.Portable, Version=20.1200.0.52, Culture=neutral, PublicKeyToken=3d67ed1f87d44c89)
at Syncfusion.OfficeChart.Implementation.Charts.ChartImpl.Clone (Syncfusion.OfficeChart.Portable, Version=20.1200.0.52, Culture=neutral, PublicKeyToken=3d67ed1f87d44c89)
at Syncfusion.DocIO.DLS.WChart.CloneImpl (Syncfusion.DocIO.Portable, Version=20.1200.0.52, Culture=neutral, PublicKeyToken=3d67ed1f87d44c89)
Hi Tuong,
We have tried to reproduce the reported problem
“NullReferenceException throws while read the Docx Word document'” using the given Word
document “file-sample_500kB.docx”, but it works properly at our end. For
your reference, we have attached the sample application which we tried to
reproduce the reported problem at our end.
Note:
Please find the input Word document in “Data” folder of above sample location.
Could
you please try the same sample application at your end and provide us
confirmation whether you are facing issues in this simple sample too.
If the issue is not reproduced using the attached sample application at your
end, then could you please modify the attached sample as an issue reproducible
sample application and share us. Thereby, we will proceed further to replicate
the same problem at our end and will provide you appropriate solution at the earliest.
Regards,
Anto Nihil S
Hi @Anto Nihil S.
I reproduced the error, it was on .net core version 3.1 and 6.0, version 2.0 didn't happen,
I also attached the code below could you help me see them
Thanks & Best Regards ,
Rider
Attachment: ConversionSample_7f2831d6_error_60c997a2.zip
Hi Rider,
We have reproduced the reported issue with "NullReferenceException throws
while importing content from one Word document to another" in our end,
and we suspect it to be a defect. We will validate this issue and update you
with more details on 17th May 2022.
Regards,
Anto Nihil S
Hi Anto Nihil S,
Thanks for the help of the team, we will wait for the next update.
Thanks & Best Regards ,
Rider
Hi Rider,
We have confirmed that reported issue
with “NullReferenceException
throws while importing content from one Word document to another” is
a defect and we have logged a defect report. Since you have been using our
weekly release (v20.1.0.52), we will include the fix for this defect in our weekly
NuGet release which is estimated to be available on 24th May 2022.
The status of this bug can be tracked through the below link:
https://www.syncfusion.com/feedback/34963/exception-is-thrown-while-importing-content-from-one-word-document-to-another
Disclaimer: “Inclusion of this solution in the weekly release may change
due to other factors including but not limited to QA checks and works
reprioritization.”
Note: If you require a patch for the reported issue in any of our
Essential Studio versions (except weekly release version), then kindly let us
know the currently installed version, so that we can provide a patch in that
version based on our SLA policy.
Regards,
Anto Nihil S
Hi Anto Nihil S,
Has this bug can be fixed yet? We are looking forward to it being fixed in this weekly release ( 24th May 2022)
Thanks & Best Regards ,
Tuong
Hi Tuong,
Sorry for the inconvenience.
We have not included the fix for this issue in our latest weekly NuGet release on tomorrow. So, we will plan to provide the custom NuGet in the latest version on tomorrow (24th May 2022).
Regards,
Anto Nihil S
Hi Tuong,
As mentioned earlier, we have prepared custom NuGet for the
mentioned issue in the latest version (v20.1.0.57) and it can be downloaded
from the below link.
https://www.syncfusion.com/downloads/support/directtrac/general/ze/syncfusion.officechart.net.core.20.1.0.57-1177104552
Note: We have planned to include this fix in our upcoming
weekly NuGet release on 31th May
2022 without further delay.
The status of this bug report can be tracked through the below link:
https://www.syncfusion.com/feedback/34963/exception-is-thrown-while-importing-content-from-one-word-document-to-another
Regards,
Anto Nihil S
Hi Anto Nihil S,
Thanks for the help of the team, we will wait for the next update.
Thanks & Best Regards,
Tuong
Hi Anto Nihil S ,
I installed the custom NuGet that you provided. For the first time in the project I am working on, the chart works fine. But the second time, I clone a new source (the same code as the first time), then I installed the custom NuGet file, but it still has the chart issue (please refer this image).
I refer to how to install the NuGet file here: https://stackoverflow.com/questions/10240029/how-do-i-install-a-nuget-package-nupkg-file-locally (please refer this image that I install nuget file).
Please help me to check this custom NuGet file again to make sure it can fix the chart issue. My company has the plan to release the product at the end of this month.
By the way, I have a question: Is there any difference between this custom NuGet file and the weekly NuGet release on 31st May 2022?
Many Thanks & Best Regards,
Tuong
Hi Tuong,
Thank you for your update.
Regarding - please help me
to check this custom NuGet file again to make sure it can fix the chart issue?:
From the given details, the reported problem “NullReferenceException throws while
importing content from one Word document to another” is resolved at our end by using the given Custom Nuget. So we have suspected you may not install the Custom
Nuget properly.
Please refer to the below KB steps to install the custom NuGet package,
https://www.syncfusion.com/kb/11556/how-to-install-the-customer-patch-nuget-in-windows-machine
Note: Kindly use the same Syncfusion product version like 20.1.0.57
in your application. Because Custom NuGet is prepared for this mentioned version(v20.1.0.57) only.
Regarding-Is
there any difference between this custom NuGet file and the weekly NuGet
release on 31st May 2022?
No. But you will get more bug fixes in the 31st May 2022 Weekly Nuget release compared to the given Custom
Nuget.
Please let us know if you have any other queries.
Regards,
Anto Nihil S
Hi Tuong,
As promised
earlier, we have included the fix for the reported issue with “NullReferenceException
throws while importing content from one Word document to another” in our
latest weekly NuGet release (v20.1.0.58).
Please use
the below link to download our latest weekly NuGet:
https://www.nuget.org/packages/Syncfusion.DocIO.Net.Core/20.1.0.58
The status
of this bug task can be tracked through the below link:
https://www.syncfusion.com/feedback/34963/exception-is-thrown-while-importing-content-from-one-word-document-to-another
Note: We will include
this fix in our 2022 Volume 2 main release which will be available in end of
June 2022.
Regards,
Suriya Balamurugan.
The post is very helpful https://www.syncfusion.com/kb/11556/how-to-install-the-customer-patch-nuget-in-windows-machine
This custom NuGet file fixed this bug.
Many thanks,
Tuong
Thank you for your update. I upgraded v20.1.0.58 and the bug is fixed.
Many thanks,
Tuong