<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Content Organiser on Matt Thornton</title>
    <link>http://localhost:1313/tags/content-organiser/</link>
    <description>Recent content in Content Organiser on Matt Thornton</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Tue, 12 Dec 2017 12:53:10 +0000</lastBuildDate><atom:link href="http://localhost:1313/tags/content-organiser/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Create SharePoint Content Organiser rules programmatically with lookup fields</title>
      <link>http://localhost:1313/tech/sharepoint/create-sharepoint-content-organiser-rules-programmatically-lookup-fields/</link>
      <pubDate>Tue, 12 Dec 2017 12:53:10 +0000</pubDate>
      
      <guid>http://localhost:1313/tech/sharepoint/create-sharepoint-content-organiser-rules-programmatically-lookup-fields/</guid>
      
        <description>&lt;p&gt;I&amp;rsquo;ve wittered on &lt;a href=&#34;https://www.matt-thornton.net/tech/sharepoint/creating-sharepoint-2010-content-organizer-rules-programmatically&#34;&gt;before&lt;/a&gt; about how much I like the content organiser in SharePoint. It&amp;rsquo;s really pretty handy. Even creating rules that target other content organisers is possible. (&lt;a href=&#34;https://www.matt-thornton.net/tech/powershell-tech/setting-content-organiser-settings-programmatically&#34;&gt;With a little trickery&lt;/a&gt;.)&lt;/p&gt;
&lt;p&gt;But since it&amp;rsquo;s SharePoint, it&amp;rsquo;s not without its quirks. I like to do as much as my dev work programmatically as possible. Every now and then you think maybe you&amp;rsquo;ve hit something you can&amp;rsquo;t script and you&amp;rsquo;ll have to resort to adding a deployment step. I was close with this.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>