We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

SSRS Export reporting using TXT � Plain Text via Aspose.Words is losing formatting

Aspose.Words Product Family
#1

We have a SSRS report in SQL Server 2005 and it when exported using Aspose.words (TXT format) it exports fine. When we export the same report in SQL Server 2014 using same Aspose.words (TXT format) the formatting is totally messed up. See three attachment (1) how reports looks in web browser, (2) how it looks when exported from SSRS 2005 using Aspose.word (txt format), and (3) how it looks when exported from SSRS 2015 using the same Aspose.word (txt format). What can be done so that when report is exported from SSRS 2014 it doesn’t lose any formatting.

The Aspose.word was installed in SQL Server 2005 long time ago by someone else. I installed trial version of Aspose.WOrds in SQL Server 2014. May be we are missing some configuration (or post-install settings) related to Aspose.words in SQL Server 2014 which might have already been done in SQL Server 2005

Also attached is the .RDL file

#2

Hi there,

Thanks for your inquiry. It would be great if you please share following detail for investigation purposes.

  • Please use the select statement (to populate the data) inside your RDL file and share it.
  • Please attach the output text file that shows the undesired behavior.
  • Please attach the output text file that shows the desired behavior.

As soon as you get these pieces of information ready, we’ll start investigation into your issue and provide you more information. Thanks for your cooperation.

PS: To attach these resources, please zip them and Click ‘Reply’ button that will bring you to the ‘reply page’ and there at the bottom you can include any attachments with that post by clicking the ‘Add/Update’ button.

Please check the following DataSet example with select statement for your kind reference.

<DataSets>
	<DataSet Name="DataSet">
		<Query>
			<DataSourceName>DataSource</DataSourceName>
			<CommandText>
				select 1 as value, ‘label1’ as label
				union all
				select 2 as value, ‘label2’ as label
				union all
				select 3 as value, ‘label3’ as label
				union all
				select 4 as value, ‘label4’ as label
			</CommandText>
		</Query>
		<Fields>
			<Field Name="value">
				<DataField>value</DataField>
				<rd:TypeName>System.Int32</rd:TypeName>
			</Field>
			<Field Name="label">
				<DataField>label</DataField>
				<rd:TypeName>System.String</rd:TypeName>
			</Field>
		</Fields>
	</DataSet>
</DataSets>
#3

Please find attached the exported output of the report from SSRS 2005 and from SSRS 2014. The one from SSRS 2005 is good and one from SSRS 2015 is not good. On the report data is being retrieved from a stored procedures which talks to multiple databases using dynamics statements and grabs data from multiple tables.

#4

For the sake of testing and explaining the issue, I have modified the report to use a single table. Attached is the updated report and the database backup (test database, and single table mytable). THat’s all you will need to test.

#5

Hi there,

Thanks for sharing the detail. Unfortunately, I am unable to restore the shared database at SQL Server 2012 because the backup is taken from SQL Server 2014.

It would be great if you please export the following query result into CSV and share it here for testing. Thanks for your cooperation.

select * from testtable

Export query result to .csv file

#6

Please find attached the script to create table and insert data in the table.

#7

Also attached the data in the csv file

#8

Hi there,

Thanks for sharing the detail. We have tested the scenario and have managed to reproduce the same issue at our side. For the sake of correction, we have logged this problem in our issue tracking system as WORDSRPT-245. You will be notified via this forum thread once this issue is resolved.

We apologize for your inconvenience.

#9

I am glad to know that you are able to reproduce the issue. Would it be possible to provide a rough time estimate when you think this issue would be resolved?
Please note that, as I mentioned earlier, the same report exports fine in SSRS 2005.
Thanks.

#10

Please note that our whole system upgrade is on hold because this issue. We would really appreciate if this can be escalated with high priority.
Thanks.

#11

Hi there,

Thanks for your inquiry. We try our best to deal with every customer request in a timely fashion, we unfortunately cannot guarantee a delivery date to every customer issue. Our developers work on issues on a first come, first served basis. We feel this is the fairest and most appropriate way to satisfy the needs of the majority of our customers.

Currently, your issue is under analysis phase. Once our product team completes the analysis of this issue, we will then be able to provide you an estimate.

Thanks for your patience and understanding.

#12

Hi there,

Thanks for your patience. Please use following workaround for this issue. Hope this helps you.

  1. open report in design mode
  2. open report properties (F4)
  3. open “Custom Properties”
  4. click [Add] button
  5. set name for new property as “AWConfiguration” (without quotes)
  6. set value for this new property - 1.65
  7. press [OK] button
  8. build & deploy updated report
#13

Hi Tahir,

The resolution you provided worked for one report but didn’t work for another report. Please find attached the .zip file. It has the actual reports, the scrip to generate tables and sample data, the PDF which will show how report looks when exported to PDF (which is good), the .txt file which show how report look with totally messed up formatting when exported using ASPOSE TXT export, another text file which shows report export fine using TXT export but when exported in SSRS 2005. We are now using this report in SSRS 2014. What do we need to do so that report exports fine in text format.

#14

Hi there,

Thanks for your inquiry. We have logged this detail in our issue tracking system. We will inform you via this forum thread once this issue is resolved. We apologize for your inconvenience.

#15

Thanks. Is there any update as to when should we expect the fix? We are on a very tight schedule to get this thing done. An early fix will be greatly appreciated.

#16

Hi there,

Thanks for your inquiry. Our product team has completed the analysis of your issue and the root cause has been identified. We have asked for the ETA of this issue from our product team. As soon as any information is shared by them, we will be more than happy to share that with you.

Thanks for your patience.

#17

Hi there,

rkapoor:
The resolution you provided worked for one report but didn’t work for another report. Please find attached the .zip file. It has the actual reports, the scrip to generate tables and sample data, the PDF which will show how report looks when exported to PDF (which is good), the .txt file which show how report look with totally messed up formatting when exported using ASPOSE TXT export, another text file which shows report export fine using TXT export but when exported in SSRS 2005. We are now using this report in SSRS 2014. What do we need to do so that report exports fine in text format.

We tested this scenario and noticed that only top-most table is shown in output documents. The second table and sub-report are disappeared. For the sake of correction, we have logged this problem in our issue tracking system as WORDSRPT-246. You will be notified via this forum thread once this issue is resolved.

We apologize for your inconvenience.

#18

I am glad to know that you were able to replicate the issue. Hope to get a quick resolution. Thanks in advance.

#19

Hi Tahir,

Could we get an early resolution. We are doing system upgrade on 12/30. This is the only issue which is pending. Is it possible to get a quick resolution on this issue?

Thanks,

#20

Hi there,

Thanks for your inquiry.

Regarding WORDSRPT-245, hopefully the fix of this issue will be available in December 2016 release (Aspose.Words for Reporting Services v16.12.0). Please note that this estimate is not final at the moment. We will be sure to inform you via this forum thread as soon as this issue is resolved.

The second issue WORDSRPT-246 is under analysis phase. Once our product team completes the analysis of this issue, we will then be able to provide you an estimate.

Thanks for your patience and understanding.