<?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 Branch Versioning APR in ArcGIS Pipeline Referencing Ideas</title>
    <link>https://community.esri.com/t5/arcgis-pipeline-referencing-ideas/branch-versioning-apr/idi-p/1540021</link>
    <description>&lt;P&gt;Lot of junk metadata created from branch versioning. Can ESRI create a way to understand this metadata. Like what happens behind the scenes when editing branch versions.&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;When using python script to append data it was loaded to the default when it was not supposed to.&lt;/LI&gt;&lt;LI&gt;Also, we have a lot of issues with branch version compatibility issues with FME jobs.&lt;/LI&gt;&lt;/OL&gt;</description>
    <pubDate>Wed, 18 Sep 2024 16:30:40 GMT</pubDate>
    <dc:creator>MarkEngle</dc:creator>
    <dc:date>2024-09-18T16:30:40Z</dc:date>
    <item>
      <title>Branch Versioning APR</title>
      <link>https://community.esri.com/t5/arcgis-pipeline-referencing-ideas/branch-versioning-apr/idi-p/1540021</link>
      <description>&lt;P&gt;Lot of junk metadata created from branch versioning. Can ESRI create a way to understand this metadata. Like what happens behind the scenes when editing branch versions.&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;When using python script to append data it was loaded to the default when it was not supposed to.&lt;/LI&gt;&lt;LI&gt;Also, we have a lot of issues with branch version compatibility issues with FME jobs.&lt;/LI&gt;&lt;/OL&gt;</description>
      <pubDate>Wed, 18 Sep 2024 16:30:40 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pipeline-referencing-ideas/branch-versioning-apr/idi-p/1540021</guid>
      <dc:creator>MarkEngle</dc:creator>
      <dc:date>2024-09-18T16:30:40Z</dc:date>
    </item>
  </channel>
</rss>

