<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>idea Prune Archiving based on dates in Data Management Ideas</title>
    <link>https://community.esri.com/t5/data-management-ideas/prune-archiving-based-on-dates/idi-p/1673236</link>
    <description>&lt;P&gt;At PG&amp;amp;E, we have a need to do bulk updates (conflation) while we are migrating to UN. To help UN data NOT get inundated by conflation, there is a need to "PRUNE" the archived data based on a given pair of dates. For eg. If we do bulk updates on a weekend, we don't want that data to be archived during that window of days.&lt;/P&gt;</description>
    <pubDate>Tue, 16 Dec 2025 01:54:49 GMT</pubDate>
    <dc:creator>VishalPahuja1</dc:creator>
    <dc:date>2025-12-16T01:54:49Z</dc:date>
    <item>
      <title>Prune Archiving based on dates</title>
      <link>https://community.esri.com/t5/data-management-ideas/prune-archiving-based-on-dates/idi-p/1673236</link>
      <description>&lt;P&gt;At PG&amp;amp;E, we have a need to do bulk updates (conflation) while we are migrating to UN. To help UN data NOT get inundated by conflation, there is a need to "PRUNE" the archived data based on a given pair of dates. For eg. If we do bulk updates on a weekend, we don't want that data to be archived during that window of days.&lt;/P&gt;</description>
      <pubDate>Tue, 16 Dec 2025 01:54:49 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-ideas/prune-archiving-based-on-dates/idi-p/1673236</guid>
      <dc:creator>VishalPahuja1</dc:creator>
      <dc:date>2025-12-16T01:54:49Z</dc:date>
    </item>
  </channel>
</rss>

