You are here:
Integration Limitations with Microsoft 365
Keep these issues and workarounds in mind when you integrate Salesforce Contracts with Microsoft 365.
| Known Limitation | Description | Resolution |
|---|---|---|
| Clause alignment behavior | When a clause is inserted with left alignment, the content of the new clause is also left-aligned. | Manually adjust the clause alignment . Modifying the alignment doesn’t affect the clause reference. |
| Image insertion issue | When attempting to insert a document clause with a cropped image into a Microsoft 365 document, the image isn't added because there is no image source (src) in the formatted content. | To move an image from a document clause to a Microsoft 365 document, copy and paste it directly into the document. |
| Metadata processing issue | Attempting to save more than 200 records in a single API call results in a metadata failure with the error message . |
Submit fewer than 200 records in an API call. |
| Download for External Review button issue | The presence of shapes or text boxes in the contract document results in the Download for External Review button failing to load. | Omit shapes and text boxes from the contract document. |
| Microsoft Word and Microsoft 365 editor feature parity issue |
|
Create the document template in Microsoft 365 editor. |
| Tab key usage causes content to lock in Microsoft 365 editor | When you press the tab key to add extra spacing within sections or clauses, it causes the Microsoft 365 editor to lock those areas. This results in two key issues:
This behavior is due to how the editor handles tab characters within content controls. |
To prevent this issue, avoid using the Tab key inside sections or clauses. To maintain spacing or indentation, press the space-bar multiple times instead of using the Tab key. This ensures content remains editable and clauses can be inserted without enabling Track Changes. |
| Section name formatting not applied when locked | When a section is inserted into a document, the section name is enclosed within a locked content control to prevent manual changes. However, in Microsoft 365 editor, you can still modify font styles and formatting inside these locked controls. This leads to inconsistencies in how section headers appear across documents. | To prevent this issue, avoid making formatting changes to section names when using the Microsoft 365 editor. |
| Document view and PDF output don’t match | When editing documents using Microsoft 365 editor, the formatting may differ from the final PDF output. This is noticeable when the “Don’t add spaces between paragraphs of same style” paragraph setting is enabled. Microsoft 365 editor and Microsoft Word render this setting differently, and the PDF reflects the Microsoft Word formatting. | To prevent this issue, don’t enable the Don’t add spaces between paragraphs of same style option while editing in Microsoft 365 editor. This ensures consistent formatting between the editor and the generated PDF. |
Did this article solve your issue?
Let us know so we can improve!
