<?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 Create Database View in ArcGIS Pro Questions</title>
    <link>https://community.esri.com/t5/arcgis-pro-questions/create-database-view/m-p/1323879#M72609</link>
    <description>&lt;P&gt;Hey guys! I created that sql expression below in Create Database View to simplify the users queries and it worked well, but I've acrossed with some issues.&lt;/P&gt;&lt;P&gt;When I made join i lost the&amp;nbsp;fields subtype_codes. Then, it remains just the associated default value.&lt;/P&gt;&lt;P&gt;Is there a way to conserve subtype_code after doing that join tables?&lt;/P&gt;&lt;LI-CODE lang="sql"&gt;SELECT adhp.name_txt, adhp.type_code, adhp.military_code, adhpsurfacearea.subtypecode, adhpsurfacearea.globalid, adhpsurfacearea.length_val, surfacecharacteristic.composition_code FROM adhp JOIN adhpsurfacearea ON adhp.gfid = adhpsurfacearea.adhp_id JOIN surfacecharacteristic ON surfacecharacteristic.gfid = adhpsurfacearea.surfacecharacteristic_id;&lt;/LI-CODE&gt;&lt;P&gt;In this case, the field is subtype_code from adhpsurfacearea.&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 30 Aug 2023 13:16:00 GMT</pubDate>
    <dc:creator>ammsgis</dc:creator>
    <dc:date>2023-08-30T13:16:00Z</dc:date>
    <item>
      <title>Create Database View</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/create-database-view/m-p/1323879#M72609</link>
      <description>&lt;P&gt;Hey guys! I created that sql expression below in Create Database View to simplify the users queries and it worked well, but I've acrossed with some issues.&lt;/P&gt;&lt;P&gt;When I made join i lost the&amp;nbsp;fields subtype_codes. Then, it remains just the associated default value.&lt;/P&gt;&lt;P&gt;Is there a way to conserve subtype_code after doing that join tables?&lt;/P&gt;&lt;LI-CODE lang="sql"&gt;SELECT adhp.name_txt, adhp.type_code, adhp.military_code, adhpsurfacearea.subtypecode, adhpsurfacearea.globalid, adhpsurfacearea.length_val, surfacecharacteristic.composition_code FROM adhp JOIN adhpsurfacearea ON adhp.gfid = adhpsurfacearea.adhp_id JOIN surfacecharacteristic ON surfacecharacteristic.gfid = adhpsurfacearea.surfacecharacteristic_id;&lt;/LI-CODE&gt;&lt;P&gt;In this case, the field is subtype_code from adhpsurfacearea.&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 30 Aug 2023 13:16:00 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/create-database-view/m-p/1323879#M72609</guid>
      <dc:creator>ammsgis</dc:creator>
      <dc:date>2023-08-30T13:16:00Z</dc:date>
    </item>
    <item>
      <title>Re: Create Database View</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/create-database-view/m-p/1323975#M72618</link>
      <description>&lt;P&gt;It seems like you could join to the lookup table and display the values instead of the codes. It would follow this pattern:&lt;/P&gt;&lt;LI-CODE lang="sql"&gt;SELECT
    adhp.name_txt,
    adhp.type_code,
    adhp.military_code,
    --adhpsurfacearea.subtypecode,
    LU.subtypevalue,
    adhpsurfacearea.globalid,
    adhpsurfacearea.length_val,
    surfacecharacteristic.composition_code
FROM
    adhp
JOIN adhpsurfacearea ON adhp.gfid = adhpsurfacearea.adhp_id
JOIN surfacecharacteristic ON surfacecharacteristic.gfid = adhpsurfacearea.surfacecharacteristic_id
JOIN [SUBTYPECODELOOKUPTABLENAME] LU ON LU.subtypecode = adhpsurfacearea.subtypecode&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 30 Aug 2023 16:23:54 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/create-database-view/m-p/1323975#M72618</guid>
      <dc:creator>DougGreen</dc:creator>
      <dc:date>2023-08-30T16:23:54Z</dc:date>
    </item>
  </channel>
</rss>

