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

Free Support Forum - aspose.com

SSRS DOCX Export - Font Spacing Factor

Hi,


In MS Word you can specify a spacing factor for the font (Under Font -> Advanced -> Spacing).
Does ASPOSE .Word SSRS support a CustomProperty to do this on export or any other mechanism ?



Thanks

Hi there,


Thanks for your inquiry. Please read about spacing factor from following documentation link.
Spacing Factor and Scaling Factor

Hope this helps you. Please let us know if you have any more queries.

Hi,


I added this to the customproperties of the textbox element and it has made no difference.


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
  • Please attach the output Word file that shows the undesired behavior.
  • Please
    attach your target Word document showing the desired behavior. You can
    use Microsoft Word to create your target Word document. We will
    investigate how you are expecting your final document be generated
    like.

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>


Hi -


Attached is the RDL and 2 word documents.

Report1_Original is the export from RDL using the customproperty

Report1_changed_manually is what I want it to look like … see font properties - > advanced -> spacing



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-232. You will be notified via this forum thread once this issue is resolved.

We apologize for your inconvenience.