<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Was on Matt Thornton</title>
    <link>http://localhost:1313/tags/was/</link>
    <description>Recent content in Was on Matt Thornton</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Wed, 19 Jun 2019 12:08:29 +0000</lastBuildDate><atom:link href="http://localhost:1313/tags/was/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Troubleshooting Word Automation Services in SharePoint</title>
      <link>http://localhost:1313/tech/sharepoint/troubleshooting-word-automation-services-in-sharepoint/</link>
      <pubDate>Wed, 19 Jun 2019 12:08:29 +0000</pubDate>
      
      <guid>http://localhost:1313/tech/sharepoint/troubleshooting-word-automation-services-in-sharepoint/</guid>
      
        <description>&lt;p&gt;Continuing the theme of obscure SharePoint issues; this one on a new topic - Word Automation Services. A client has a new requirement to automate some documents and using Word templates and converting them to PDF all from a Nintex workflow would be&amp;hellip; nifty. So away we go.&lt;/p&gt;
&lt;p&gt;In Word, we created a Word document and then inserted some ‘Content Controls&amp;rsquo; - have some options here, but for proof of concept, started with a simple text control. Then in the Developer tab of the ribbon, you can edit the properties of the control and give it a title. Save the document and upload to a document library in SP.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>