in the post from the 04-12-2013
I explained the problem with cropped text in my reports and I was very happy to see that it was fixed.
But few day ago I got a similar behavoir. The text is cropped again and it depends on the configuration of the page break. When I use the normal config I got some annoying page breaks at positions I dont want. When I use the config “None” the text got cropped again.
I attached a report file that contains a very common report with fixed data that is similar to the data out of the data base.
Please check that and give me an answer because I must rely on the rendering.
And we need the floating text because the page breaks are not useful where they are.
I have tested the scenario and have not found the shared issue while using latest version of Aspose.Words for Reporting Services 4.1.0. Please upgrade to the latest version (v 4.1.0) from here and let us know how it goes on your side. Hope this helps you. I have attached the output Doc file with this post for your kind reference.
thanks for the quick reply. I only looked for a new version few days ago.
The last two days I tried different configurations to check if the problem may depend on my reports.
I didn’t see the new version, thanks for the hint! I will check it at Monday.
I will post a message if everything works well or not.
today I tested the new version of Aspose.Word and I have bad news.
When I render my example report I got the cropped text again.
What
I didn’t see at the weekend is that your attached report is in the
nested table format, the same format that the integrated renderer from
Microsoft produces.
Please remember that the nested table format
is a bad solution for my colleagues, because they have to edit the word
file afterwards. This may be an option for this kind of report but I
have reports with much more tables and textboxes.
Here are my settings to get the things a little straighter:
Microsoft SQL Server 2008 R2 Standard (including SSRS) using 4-1.dll (manual Installation)
Microsoft Visual Studio 9.0 (from SQL Tools) using 4-1.dll (manual installation)
I use following rendering extensions:
AWDOC with “default” page break behavior (see attachment: 2013-09-30_G_Aspose_Text.docx)
AWDOX with the “None” page break behavior (see attachment: 2013-09-30_G_Aspose_Test .docx)
Both
reports are rendered out of the SSRS but the same cropping are happens
when I use the Visual Studio. At the moment I use the default page break
and my colleagues have to delete them, but I’m afraid of the day when
the cropping starts here again too.
My questions are:
Witch rendering extension you use for your example?
Did I make some mistakes in my report (layout failure or something else)?
What is the Aspose preferred rendering format for such reports?
When would that bug might be fixed?
Please do not hesitate to contact me.
Best regards Maik
Loewe@TUD:
I only looked for a new version few days ago.
The last two days I tried different configurations to check if the problem may depend on my reports.
I didn’t see the new version, thanks for the hint! I will check it at Monday.
You can enable email subscription for new releases from following page by clicking the ‘Enable Email Subscription’ button. https://releases.aspose.com/words/reportingservices/
Once you have enabled the email subscription from above page, you will get the notification for new releases via email.
I am working on your query at following post and will update you asap. https://forum.aspose.com/t/50182
Witch rendering extension you use for your example?
Did I make some mistakes in my report (layout failure or something else)?
What is the Aspose preferred rendering format for such reports?
When would that bug might be fixed?
What I didn’t see at the weekend is that your attached report is in the nested table format, the same format that the integrated renderer from Microsoft produces.
Thanks for your inquiry. I attached the incorrect document in my post here. Please accept my apologies for your inconvenience.
I have managed to reproduce the page break issue at my side. I have attached the output documents with this post. I have logged this issue as WORDSRPT-147 in our issue tracking system and have linked this forum thread to the same issue and you will be notified via this forum thread once this issue is resolved. We apologize for your inconvenience.
Loewe@TUD:
When I render my example report I got the cropped text again.
Both reports are rendered out of the SSRS but the same cropping are happens when I use the Visual Studio. At the moment I use the default page break and my colleagues have to delete them, but I’m afraid of the day when the cropping starts here again too.
It would be great if you please share some more detail about ‘Cropped Text’ issue. I will investigate the issue on my side and provide you more information. I have only faced the page break issue and have logged this issue in our issue tracking system.
Hi Maik,
Thanks for your patience.
Regarding WORDSRPT-147,
it is to update you that our development team has completed the
analysis of this issue and has come to a conclusion that this issue has been closed with ‘‘Won’t Fix’’ resolution.
Please read the limitation of HTML Formatting from here: https://docs.aspose.com/words/reportingservices/html-formatting/ “If HTML text is spread over multiple pages, most likely it will be exported as plain text.”.
So in order to workaround your issue it is necessary either 1) do not use MarkupType=HTML, or 2) set option None. Please read following documentation link for your kind reference. https://docs.aspose.com/words/reportingservices/page-breaks/
The worst at this “won’t fix” situation is that the provided solutions don’t fit my requirements.
The first is that we using HTML Boxes to edit parts of the final report in the software. The benefit is that my colleagues can see a part of the report result before it is rendered. So they have the edited text and the information in the software and don’t need to look at the printed report.
The second point is that the cropped text problem only exists when I chose the “none page break” option. The default option works well at the moment.
I know that I have to accept that point but I am not very happy about this.
The funny thing is that my supervisor asks me about the current state and a wider dissemination and I don’t know what I should say.
Hi Maik,
Please accept my apologies for your inconvenience.
We do understand your situation. I am afraid, this issue won’t be fixed due to the limitation of HTML Formatting. Please read following documentation link. https://docs.aspose.com/words/reportingservices/html-formatting/
Please try following workaround to solve this issue.