<?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 Re: How to Associate Documents with Polygon Features in Portal and Link to SharePoint in ArcGIS Enterprise Questions</title>
    <link>https://community.esri.com/t5/arcgis-enterprise-questions/how-to-associate-documents-with-polygon-features/m-p/1561832#M41040</link>
    <description>&lt;P&gt;I have accomplished this one way using SharePoint and seen another way possible at our local County Assessor's office.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;SharePoint Method&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Adding a field to the feature layer named something like "RelatedDocumentURL" or something like that will allow you to paste in a url for the SharePoint directory containing the related documents. I would ensure that the link to the directory was modified so that users accessing that only had permission to view documents. Otherwise, they end up getting prompted for a login, which fails. After adding these urls to the field for each feature, a popup can &lt;A href="https://pro.arcgis.com/en/pro-app/latest/help/mapping/navigation/use-hyperlinks-in-pop-ups.htm" target="_self"&gt;display that field value as a hyperlink in various ways&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;If adding individual links to each parcel sounds nearly impossible...&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Alternative Method&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;A custom web application that allows navigation by parcel number should be developed. This requires the documents to be stored in a way that is either retrievable from a database or from a web accessible repository by parcel number. Then, in the popups for the parcel layer, you create an attribute expression that builds a url like: var url = "&lt;A href="https://domainname.com/" target="_blank"&gt;https://domainname.com/&lt;/A&gt;" + $feature.parcel_number. Then, add that attribute expression to popups according to the previously linked documentation.&lt;/P&gt;&lt;P&gt;Neither of these methods is easier. Both require that the documents be indexed somehow. I feel like the Alternative Method puts the work of organizing documents and providing means of displaying them back in the court of the assessors and clerks and allows GIS admins/analysts to provide a means of referencing them instead of doing much of the job of someone in another role.&lt;/P&gt;</description>
    <pubDate>Fri, 22 Nov 2024 18:56:38 GMT</pubDate>
    <dc:creator>DougGreen</dc:creator>
    <dc:date>2024-11-22T18:56:38Z</dc:date>
    <item>
      <title>How to Associate Documents with Polygon Features in Portal and Link to SharePoint</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-questions/how-to-associate-documents-with-polygon-features/m-p/1561785#M41038</link>
      <description>&lt;P&gt;I need to associate a large number of documents with a polygon feature layer published in Portal. The goal is for users to click on a polygon and see a pop-up containing a field with a URL. Clicking this URL should open a document library in SharePoint that contains all the documents associated with the polygon.&lt;/P&gt;&lt;P&gt;The documents and polygons share a common ID, which can be used as the link between them. However, I am unsure how to configure this mechanism in Portal or how best to set up the integration with SharePoint.&lt;/P&gt;&lt;P&gt;After investigating the Parcel Fabric Data Model, I’ve determined it is not suitable for this situation or the desired functionality.&lt;/P&gt;&lt;P&gt;Does anyone have recommendations or examples of how to configure this setup in Portal? Any advice on integrating SharePoint document libraries with feature layer attributes would also be appreciated.&lt;/P&gt;</description>
      <pubDate>Fri, 22 Nov 2024 17:08:38 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-questions/how-to-associate-documents-with-polygon-features/m-p/1561785#M41038</guid>
      <dc:creator>Daniel_Quinn</dc:creator>
      <dc:date>2024-11-22T17:08:38Z</dc:date>
    </item>
    <item>
      <title>Re: How to Associate Documents with Polygon Features in Portal and Link to SharePoint</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-questions/how-to-associate-documents-with-polygon-features/m-p/1561832#M41040</link>
      <description>&lt;P&gt;I have accomplished this one way using SharePoint and seen another way possible at our local County Assessor's office.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;SharePoint Method&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Adding a field to the feature layer named something like "RelatedDocumentURL" or something like that will allow you to paste in a url for the SharePoint directory containing the related documents. I would ensure that the link to the directory was modified so that users accessing that only had permission to view documents. Otherwise, they end up getting prompted for a login, which fails. After adding these urls to the field for each feature, a popup can &lt;A href="https://pro.arcgis.com/en/pro-app/latest/help/mapping/navigation/use-hyperlinks-in-pop-ups.htm" target="_self"&gt;display that field value as a hyperlink in various ways&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;If adding individual links to each parcel sounds nearly impossible...&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Alternative Method&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;A custom web application that allows navigation by parcel number should be developed. This requires the documents to be stored in a way that is either retrievable from a database or from a web accessible repository by parcel number. Then, in the popups for the parcel layer, you create an attribute expression that builds a url like: var url = "&lt;A href="https://domainname.com/" target="_blank"&gt;https://domainname.com/&lt;/A&gt;" + $feature.parcel_number. Then, add that attribute expression to popups according to the previously linked documentation.&lt;/P&gt;&lt;P&gt;Neither of these methods is easier. Both require that the documents be indexed somehow. I feel like the Alternative Method puts the work of organizing documents and providing means of displaying them back in the court of the assessors and clerks and allows GIS admins/analysts to provide a means of referencing them instead of doing much of the job of someone in another role.&lt;/P&gt;</description>
      <pubDate>Fri, 22 Nov 2024 18:56:38 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-questions/how-to-associate-documents-with-polygon-features/m-p/1561832#M41040</guid>
      <dc:creator>DougGreen</dc:creator>
      <dc:date>2024-11-22T18:56:38Z</dc:date>
    </item>
    <item>
      <title>Re: How to Associate Documents with Polygon Features in Portal and Link to SharePoint</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-questions/how-to-associate-documents-with-polygon-features/m-p/1562017#M41043</link>
      <description>&lt;P&gt;What do you mean by saying "&lt;SPAN&gt;The documents and polygons share a common ID"? the key is to get the map from ID and document URL. then you can create a related table in your enterprise Geodatabase. This is static though.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;It will be tricky to have a seamless system integration, still possible if you can infer the document url from the ID.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 24 Nov 2024 13:21:11 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-questions/how-to-associate-documents-with-polygon-features/m-p/1562017#M41043</guid>
      <dc:creator>simoxu</dc:creator>
      <dc:date>2024-11-24T13:21:11Z</dc:date>
    </item>
  </channel>
</rss>

