36
V

CRM 2016 | When generating (Export) a Word document and using a multiple lines of text field that contains multiple lines of text, the text is generated as a single line of text

Vishal Hemdev on 4/28/2016 1:30:00 AM

On 2016 Environment
Create a new Account record, enter the mandatory fields
In description text box enter the text in format
1
2
3
4
5
6
Abc
XYZ
Save the Account record,
Click the ellipses and click Word Template --> Account Summary
Open the document in Microsoft Word when you see the description test box you will see the data in
1 2 3 4 5 6 Abc XYZ format

Ask/Suggestion: Word document should display the description test box in the same format as it is save din CRM Interface.

Category: Microsoft Office Integration
STATUS DETAILS
Under Review
Ideas Administrator

Administrator on 8/14/2017 6:24:02 AM

Thanks for your feedback. we will look into this.

Comments

V

V

RE: CRM 2016 | When generating (Export) a Word document and using a multiple lines of text field that contains multiple lines of text, the text is generated as a single line of text

This was fixed in Update rollup 2.2 (Both on Premise and online). KB4046795. 

Category: Microsoft Office Integration

V

V

RE: CRM 2016 | When generating (Export) a Word document and using a multiple lines of text field that contains multiple lines of text, the text is generated as a single line of text

I absolutly second this request.

It is currently not possible to get muli-line text from CRM into Word in the same format, all linefeeds are cut out.

This includes the composite fields for address, these are all exported in one line as well, which is very unpleasent.

Category: Microsoft Office Integration

V

V

RE: CRM 2016 | When generating (Export) a Word document and using a multiple lines of text field that contains multiple lines of text, the text is generated as a single line of text

I also second this request. This is actually how the composite address field previously worked and I can't fathom why it was changed.

My organisation has just upgraded to Dynamics 365 after postponing as long as possible and the composite address field behaved this way before the upgrade (Dynamics CRM Online).

Category: Microsoft Office Integration