<?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 Provide settings for feature attachment delivery in Distributed Collaborations in ArcGIS Enterprise Ideas</title>
    <link>https://community.esri.com/t5/arcgis-enterprise-ideas/provide-settings-for-feature-attachment-delivery/idi-p/1344679</link>
    <description>&lt;P&gt;When sharing feature layers as copies in a distributed collaboration there is currently a size limitation of 1 GB; if the feature layer is over 1 GB the layer is shared as a reference rather than as a copy (&lt;A href="https://enterprise.arcgis.com/en/portal/latest/use/common-questions-for-distributed-collaboration.htm#anchor70" target="_self"&gt;FAQ Link&lt;/A&gt;).&amp;nbsp; I currently have layers in my geodatabase that I would like to share as copies to ArcGIS Online but cannot because of the number of feature attachments in the layer.&amp;nbsp; As a possible solution to this problem, I would like to propose that the distributed collaboration settings be enhanced to include attachment controls similar to those that are found in the Field Maps interface in ArcGIS Enterprise:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Field Maps Attachment Settings.JPG" style="width: 400px;"&gt;&lt;img src="https://community.esri.com/t5/image/serverpage/image-id/84753i390D7A830F72153D/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Field Maps Attachment Settings.JPG" alt="Field Maps Attachment Settings.JPG" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;With these controls provided at the collaboration, group, or service level users could decide how features and attachments are synchronized with the parent organization.&lt;/P&gt;</description>
    <pubDate>Wed, 01 Nov 2023 20:29:57 GMT</pubDate>
    <dc:creator>tmichael_wpjwa</dc:creator>
    <dc:date>2023-11-01T20:29:57Z</dc:date>
    <item>
      <title>Provide settings for feature attachment delivery in Distributed Collaborations</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-ideas/provide-settings-for-feature-attachment-delivery/idi-p/1344679</link>
      <description>&lt;P&gt;When sharing feature layers as copies in a distributed collaboration there is currently a size limitation of 1 GB; if the feature layer is over 1 GB the layer is shared as a reference rather than as a copy (&lt;A href="https://enterprise.arcgis.com/en/portal/latest/use/common-questions-for-distributed-collaboration.htm#anchor70" target="_self"&gt;FAQ Link&lt;/A&gt;).&amp;nbsp; I currently have layers in my geodatabase that I would like to share as copies to ArcGIS Online but cannot because of the number of feature attachments in the layer.&amp;nbsp; As a possible solution to this problem, I would like to propose that the distributed collaboration settings be enhanced to include attachment controls similar to those that are found in the Field Maps interface in ArcGIS Enterprise:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Field Maps Attachment Settings.JPG" style="width: 400px;"&gt;&lt;img src="https://community.esri.com/t5/image/serverpage/image-id/84753i390D7A830F72153D/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Field Maps Attachment Settings.JPG" alt="Field Maps Attachment Settings.JPG" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;With these controls provided at the collaboration, group, or service level users could decide how features and attachments are synchronized with the parent organization.&lt;/P&gt;</description>
      <pubDate>Wed, 01 Nov 2023 20:29:57 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-ideas/provide-settings-for-feature-attachment-delivery/idi-p/1344679</guid>
      <dc:creator>tmichael_wpjwa</dc:creator>
      <dc:date>2023-11-01T20:29:57Z</dc:date>
    </item>
  </channel>
</rss>

