Aspose.Words for Reporting Service

Hi,
I have 2 issues when Reporting Service rendering via Aspose.Words, I am using version 3.0.3.0.

  1. HTML Tag is not recognized. For example, you type something in word document, bold and underline some of the text, and giving some bulleting on it. Next copy the text from word document and paste it to a rich text editor, and save into the DB, this will save the html tag into DB. The last step is, generate a report in reporting service via Aspose.Words, this report will read the html tag and generate it to word document. Unfortunately, failed to generate due to the html tag that copy from word document. It’s working if there is no html tag.
  2. There are extra blank pages between pages even though i have configured the “OnEachPage”.

Please look into this issue and provide me an alternative. Thanks.

Hi

Thanks for your request.

  1. Maybe you should enable “EnableHTMLFormatting” option as described here:
    https://docs.aspose.com/words/reportingservices/html-formatting/
  2. Could you please attach your RDL report for testing? We will investigate the issue and provide you more information.

Best regards.

Hi,
Yes, HTML is enabled.
Could you try out the steps that I mentioned above?

Hi

Could you please extract HTML from your database and attach it here? Different rich text editors can save HTML differently. So please attach sample HTML you are trying to insert into a report.
Also, please attach your RDL report; this will help us to investigate the problem with extra blank pages.
Best regards.

Hi,
The txt file is the html text which was saved into Database. And rdl file actually has nothing much to see, just a field which extract the html text and print on the report.

Hi

Thank you for additional information. I logged your request in our defect database as issue #9087. The developer who is responsible for Aspose.Words for Reporting Services will take a look on it shortly.
Best regards.

Hi,
Could you please expedite this issue. Thanks.

Hi,
I still do not get any reply on this issue?

Hi,
Sorry for delay. Please expect a reply in a few hours.

Ok, how long do you think we have to wait for the solution?

Hi,
The problem turned out to be more serious than I thought before. Let me explain.
I have tested your report and succeeded to generate a document with correct HTML formatting (see attached), but with extra blank pages because the height of the textbox was calculated incorrectly. What is the document you are getting, does it look similarly?
First off, you should avoid any page breaks within the formatting. The reason is that the breaking algorithm never knows it deals with HTML formatting. This may lead to putting a break somewhere in the middle of a tag and therefore to corrupting the HTML. So the correct option to use is None. I will mention this in the documentation.
Secondly, the height of the textbox is also calculated based on the HTML code. The calculated height, as you understand, is normally much bigger than that of the formatted text because of the markup. That’s why the renderer inserts spacing after the text.
The core of the problem is that the HTML formatting recognition feature is quite limited. We added it because we wanted to use the power of the DocumentBuilder.InsertHtml method, but we warned the users that the feature has some limitations:
https://docs.aspose.com/words/reportingservices/html-formatting/
I will add the extra spacing problem to the list of possible side effects.
Regarding the fixes, you specified that you never get the formatted text at all. This is what should not happen and is surely fixable. Did you mean the whole markup appears in the document rather than bold, bullets etc?

Hi,
I do not see any attachment in the post.

  1. In version 3.0.3, you are saying the smart page break is fixed, but the header is generated wrongly. The page number is wrong, the page header detail is wrong.
  2. If None, there are 3 blank pages after the rich text content.

We cannot afford to have the 2 limitation above, we bought this product but realize this limitation at later stage, hopefully can get a solution this the issues.
Anyway no problem if we export to RTF, but there is issue if we export to word document.

Sorry for missing the attachment. Please have a look.

  1. Could you please attach a report that would allow me to reproduce this issue? It seems like this is not the one you attached, correct?
  2. Yes, that’s what I explained in the post above. The HTML formatting feature may have some side effects which are hard to fix. I will try to fix the spacing problem, but cannot promise anything.

The attachment you uploaded also has the blank pages issue which we are facing now.
We also have page number and application number showing as header on each page, but with the most latest version of Aspose word, the header information is not generated correctly. The page number is shown wrongly and application number is not shown at all.

I explained the reason why those blank pages appear. Unfortunately, this is a side effect of the HTML formatting feature and I can’t fix it anytime soon.
But the page number problem is obviously fixable. I need your report to reproduce this issue. Do I correctly understand that this problem occurs with another report, not the one you have attached?
Thanks.

Attached is the sample report.
When we set PageBreak to “None”, the page number always shows the total pages of generated report. But if we set PageBreak to “OnEachPage”, then the page number is showing correctly, but giving us error in those rich text content.
Please help to fix the error in header and also the unknown blank pages.

Hi,
I have fixed the first issue. Now page number is displayed correctly and the “Application No” textbox is visible whatever page breaks mode is set. A hotfix of the product will be available on Monday.
Regarding the excessive spacing issue - as I stated earlier, I can’t fix it right at the moment. The best workaround I could end up with is as follows:

  1. Set PageBreaks to None in the configuration file.
  2. Set CanGrow to false for the textbox containing the HTML data.
  3. Set CanShrink to true for that textbox.

In this case, there is still a little spacing after the formatted text, but no blank pages anymore. Please try this trick out and let me know if this works.
Thanks.

Hi,
When and where can I have the hotfix released to us? I still couldn’t find it in download section. Thanks.

It will be released in a few hours.