When I output a report to txt using the Plain Text via Aspose.Words addon, I get the following character ( ☥ ) at the end of a section and not sure why its showing up. Need it to go away. Anyone have any ideas? It’s not showing up when I output a PDF file so it’s definitely something to do with txt. I’m using a Trial version. Thanks.
Hi Brian,
Thanks for your inquiry. It would be great
If you please use the select statement (to populate the data) inside your
RDL file and share that RDL file with us. I will investigate the issue
on my side and provide you more information.
<DataSets>
<DataSet Name=“DataSet1”>
<Query>
<DataSourceName>DataSource1</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>
Hi Tahir,
I have attached a sample RDL. If you run this it will generate this Unicode character: U+2625
or ☥. Please find out why this is getting generated and how to remove it from the txt file.
Thanks,
Brian
Hi Brian,
Thanks for sharing the detail. I
have tested the scenario and have managed to reproduce the same issue
at my side. For the sake of correction, I have logged this problem in
our issue tracking system as WORDSRPT-215. I 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.
Hi Aspose,
Was just wondering if there’s been any update on this. Can you provide an ETA or anything?
Thanks,
Brian
Hi Brian,
Thanks for your inquiry. I would like to
share with you that issues
are addressed and resolved based on first come first serve
basis. Currently, your issue is under analysis. I am afraid, we can’t provide you any reliable estimate at the
moment. Once your issue is analyzed, we will then be able to provide you
an estimate.
Thanks for your patience and understanding.
Hello Tahir,
Appreciate that this issue is currently under analysis but we have some business critical client reports that require this functionality and any insight on a workaround or eta would be very much appreciated. This has been escalated at our side so I’m anxious to work with you guys to come up with a solution…asap.
Thanks,
Brian
Hi Brian,
Thanks for your inquiry. Unfortunately, there is no workaround for this issue. I am afraid, we can’t provide you any estimate at the
moment. Once your issue is analyzed, we will then be able to provide you
an estimate.
Thanks for your patience.
Hello Tahir,
Has the analysis on this bug finished yet? I’m keen to find out if analysis has been completed and the outcome of that etc…
Thanks,
Brian
Hi Brian,
Thanks for your inquiry. I have verified the status of this issue from our issue tracking system and like to share with you that this issue is under analysis phase. I 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 and understanding.
Hello Tahir,
Any update on this issue yet, another month has passed and I would appreciate an update.
Thanks,
Brian
I have verified the status of WORDSRPT-215 from our issue tracking system and like to share with you that this issue has been resolved. Its fix will be available in next version of Aspose.Words for Reporting Services. Hopefully, the next version of Aspose.Words for Reporting Services will be available at the end of June 2015. We will inform you once this release is published.
Thanks for your patience.
http://www.aspose.com/community/files/52/ssrs-rendering-extensions/aspose.words-for-reporting-services/entry629228.aspx
The issues you have found earlier (filed as WORDSRPT-215) have been fixed in this Aspose.Words for Reporting Services release.
This message was posted using Notification2Forum from Downloads module by aspose.notifier.