<?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>topic Did Pro/SQL change where attachment relationship classes are stored at some point? in ArcGIS Pro Questions</title>
    <link>https://community.esri.com/t5/arcgis-pro-questions/did-pro-sql-change-where-attachment-relationship/m-p/1570290#M91431</link>
    <description>&lt;P&gt;I have a big old legacy GIS environment that I manage - it's been built up to its current form from at least the 10.x days, and potentially the 9.x days.&amp;nbsp; For as long as I can remember, any feature classes that have an attachment relationship has looked like: FC lives in dataset, attachment relationship class and table both live at the GDB level.&lt;/P&gt;&lt;P&gt;Recently I've been having an issue where feature classes that are updated with new attachments fail to collaborate in our distributed collaboration due to code":500,"message":"Unable to synchronize replica.","details":["Importing delta data changes failed."]&lt;/P&gt;&lt;P&gt;I do have a case open with esri and we found that copy-pasting one of the FCs in question into the same dataset fixes the issue - but what happens when you do this (create a new FC with attachments enabled in our up-to-date environment) is the attachment class now appears within the dataset (with the attachment table still living at the top level of the GDB).&lt;/P&gt;&lt;P&gt;I am wondering if this is a documented change - entirely possible it's been this way for years and I just haven't noticed.&amp;nbsp; Any insight would be great.&amp;nbsp; Thanks!&lt;/P&gt;</description>
    <pubDate>Thu, 19 Dec 2024 17:59:49 GMT</pubDate>
    <dc:creator>valenj88</dc:creator>
    <dc:date>2024-12-19T17:59:49Z</dc:date>
    <item>
      <title>Did Pro/SQL change where attachment relationship classes are stored at some point?</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/did-pro-sql-change-where-attachment-relationship/m-p/1570290#M91431</link>
      <description>&lt;P&gt;I have a big old legacy GIS environment that I manage - it's been built up to its current form from at least the 10.x days, and potentially the 9.x days.&amp;nbsp; For as long as I can remember, any feature classes that have an attachment relationship has looked like: FC lives in dataset, attachment relationship class and table both live at the GDB level.&lt;/P&gt;&lt;P&gt;Recently I've been having an issue where feature classes that are updated with new attachments fail to collaborate in our distributed collaboration due to code":500,"message":"Unable to synchronize replica.","details":["Importing delta data changes failed."]&lt;/P&gt;&lt;P&gt;I do have a case open with esri and we found that copy-pasting one of the FCs in question into the same dataset fixes the issue - but what happens when you do this (create a new FC with attachments enabled in our up-to-date environment) is the attachment class now appears within the dataset (with the attachment table still living at the top level of the GDB).&lt;/P&gt;&lt;P&gt;I am wondering if this is a documented change - entirely possible it's been this way for years and I just haven't noticed.&amp;nbsp; Any insight would be great.&amp;nbsp; Thanks!&lt;/P&gt;</description>
      <pubDate>Thu, 19 Dec 2024 17:59:49 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/did-pro-sql-change-where-attachment-relationship/m-p/1570290#M91431</guid>
      <dc:creator>valenj88</dc:creator>
      <dc:date>2024-12-19T17:59:49Z</dc:date>
    </item>
  </channel>
</rss>

