<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">

 
 
  <channel>
    <title>Export Sets on ServiceNow Developer Blog</title>
    <link>https://developer.servicenow.com/blog.do?p=/tags/export-sets/</link>
    <description>Recent content in Export Sets on ServiceNow Developer Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 05 Oct 2017 14:56:41 +0000</lastBuildDate>
    
        
        
         
        <atom:link href="https://developer.servicenow.com/blog.do?p=/tags/export-sets/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Exporting Data with Sys IDs</title>
      <link>https://developer.servicenow.com/blog.do?p=/post/exporting-data-with-sys-ids/</link>
      <pubDate>Thu, 05 Oct 2017 14:56:41 +0000</pubDate>
      
      <guid>https://developer.servicenow.com/blog.do?p=/post/exporting-data-with-sys-ids/</guid>
      <description>ServiceNow provides a number of ways to export data from the platform. All of these methods are simple to use, but something that isn&amp;rsquo;t always obvious is how to include the Sys ID value associated with a record in the export.
Depending on how you plan to use the exported data, having the Sys ID is important. If you plan to do any kind of reconciliation or bring that data back into the platform in the future, having this value is critical.</description>
    </item>
    
  </channel>
</rss>