<?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 Attachment updates in ArcGIS Pro Ideas</title>
    <link>https://community.esri.com/t5/arcgis-pro-ideas/attachment-updates/idi-p/932919</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;Currently - I have almost 6000 attachments linked to my Water GIS system. Most of them are composed of .PDF construction as-builts and .JPEG field phtotos. However - these .PDFs are constantly being updated. The problem I have is when one of the "Native" external files are modified and saved - the editor has to go into ArcMap - remove that attachment and reattach the same file. This makes it really frustrating when there are alot of attachments being updated on a regular basis. it would be nice that when the external native file is modified and saved - nothing has to be done to the attachment in ArcMap.

&lt;!-- content transformation source ID: 087E00000004QeL --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 05 Dec 2012 16:09:37 GMT</pubDate>
    <dc:creator>ModernElectric</dc:creator>
    <dc:date>2012-12-05T16:09:37Z</dc:date>
    <item>
      <title>Attachment updates</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/attachment-updates/idi-p/932919</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;Currently - I have almost 6000 attachments linked to my Water GIS system. Most of them are composed of .PDF construction as-builts and .JPEG field phtotos. However - these .PDFs are constantly being updated. The problem I have is when one of the "Native" external files are modified and saved - the editor has to go into ArcMap - remove that attachment and reattach the same file. This makes it really frustrating when there are alot of attachments being updated on a regular basis. it would be nice that when the external native file is modified and saved - nothing has to be done to the attachment in ArcMap.

&lt;!-- content transformation source ID: 087E00000004QeL --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 05 Dec 2012 16:09:37 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/attachment-updates/idi-p/932919</guid>
      <dc:creator>ModernElectric</dc:creator>
      <dc:date>2012-12-05T16:09:37Z</dc:date>
    </item>
    <item>
      <title>Re: Attachment updates</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/attachment-updates/idc-p/932920#M3373</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;When using geodatabase attachments the file itself is loaded into the relational database as a blob. &amp;nbsp;For your workflow this, in effect, creates two copies: one stored on the file system and one in the relational database. &amp;nbsp;It sounds like you only want one copy of the file to exist. &amp;nbsp;For this, you can consider making the file folder(s) available as a web share and creating a field to hyperlink to the file's location (e.g. http:\\myFileShare\ww\12101.pdf). &amp;nbsp;This way, you will always be acecssing the version of the file that is shared on the file system.&lt;BR /&gt;

&lt;!-- content transformation source ID: 00aE000000260rH --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 05 Dec 2012 22:03:43 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/attachment-updates/idc-p/932920#M3373</guid>
      <dc:creator>PhilHolleran</dc:creator>
      <dc:date>2012-12-05T22:03:43Z</dc:date>
    </item>
    <item>
      <title>Re: Attachment updates</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/attachment-updates/idc-p/932921#M3374</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;It would be nice if we could set the datasource to be either within the GDB or on a network share...&lt;BR /&gt;I know that my DBA's aren't keen on storing data within the database like this...

&lt;!-- content transformation source ID: 00aE000000262XT --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 Dec 2012 05:07:27 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/attachment-updates/idc-p/932921#M3374</guid>
      <dc:creator>CoryWilliams</dc:creator>
      <dc:date>2012-12-07T05:07:27Z</dc:date>
    </item>
    <item>
      <title>Re: Attachment updates</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/attachment-updates/idc-p/932922#M3375</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;I agree it would be good if the attachment is &lt;EM&gt;managed&lt;/EM&gt; or &lt;EM&gt;unmanaged&lt;/EM&gt; just like a raster catalog. I would find it very helpful the ability to link an attachment to an external file rather than something that gets sucked into the geodatabase.

&lt;!-- content transformation source ID: 00aE00000028GD7 --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Feb 2013 10:45:44 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/attachment-updates/idc-p/932922#M3375</guid>
      <dc:creator>DuncanHornby</dc:creator>
      <dc:date>2013-02-01T10:45:44Z</dc:date>
    </item>
    <item>
      <title>Re: Attachment updates</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/attachment-updates/idc-p/932923#M3376</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;We are in the same position.&amp;nbsp; Our record mapping is constantly being updated.&amp;nbsp; It would be better to have the option for attachements to only store the path to the file on a file server.&amp;nbsp; There would only be one copy of a record map and the attachement would always point to the newest version.&amp;nbsp; It would also keep the geodatabase from growing exponentially.

&lt;!-- content transformation source ID: 00aE0000002zDz5 --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 03 Jun 2013 15:04:44 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/attachment-updates/idc-p/932923#M3376</guid>
      <dc:creator>RobertMateja</dc:creator>
      <dc:date>2013-06-03T15:04:44Z</dc:date>
    </item>
    <item>
      <title>Re: Attachment updates</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/attachment-updates/idc-p/932924#M3377</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;I agree with the below comments.&amp;nbsp; In addition to attachment changes, I do not want to store the attachments in 2 locations if I already have a robust document management system.

&lt;!-- content transformation source ID: 00aE0000004LigH --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 12 Nov 2013 20:47:43 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/attachment-updates/idc-p/932924#M3377</guid>
      <dc:creator>MichaelVolz</dc:creator>
      <dc:date>2013-11-12T20:47:43Z</dc:date>
    </item>
  </channel>
</rss>

