Formatting issues with Import from Microsoft Word

[Jon Collins2]

Hi Folks, has anyone found a good work around for leveraging the Import from Word tool for Knowledge Management?

I find that I spend so much time fixing formatting issues with documents that I import as articles, that it's just easier to recreate the content in ServiceNow, as an article, using the WYSIWYG editor. With that said, many of my stakeholders are providing me with Word documents and re-creating all of them is getting quite labor-intense

• Has anyone developed a simplified template or guidelines that minimize re-formatting needs with the MS Word Import?
• How are others handling formatting issues with articles imported from Word? 

Thanks! 

[DavidBReynolds]

My question is similar and may explain Jon Collins' issue as well. We have style sheets listed as a required field in ServiceNow. I set up my styles in Word to mimic those in ServiceNow so they look similar initially. However, clicking the Style sheet overwrites the content, essentially making this feature worthless.

If you do not have stylesheets set as a required field, though, consider creating a Word template and having everyone use it. That should ensure all headings and paragraph formatting is consistent.

Have people open the .dot template then save the document as a .docx or .doc file. That should solve your formatting issues. 

I hope this helps.

[Community Alums]

When you manually copy the text of word into Knowledge Article body in ServiceNow it ask us to remove or keep formatting. Does anyone know how we can achieve the same thing while using Import Articles using word document?

I need to understand if we can use a code in the backend to enable to same keep/remove formatting option while importing word docs using import article option in ServiceNow.

[Tom_T]

IMHO the the word import functionality is pre-beta material. This is just a given functionality full errors, failure and what ever... Just to be able to do marketing with M365 integration slogan.

Standard bullets in word are coverted to some strange squares

There are serious formatting issues even when just using standard heading

Pictures are a gamble - sometimes yes, sometimes no. SVG (which is a web format for graphics) doesn't get imported at all

We do not have the capacity to re-create all the docs manually. I tried to save my documents as an .html and then back to .docx. Even that doesn't work.

On top of all that the red-lining process needs to be outside of SNOW. Since red-lining is team effort the OneDrive connector recommendation is the next joke showing that SNOW dev has not understand the difference between a SharePoint and a OneDrive imho.

I do hope they will make some major step forward with Xanadu release. This is promising SharePoint integration. And maybe some improvment on the whacky docx import.
Example - original word:

Result - just see the standard bullets conversion. No graphics included