<?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 Add Join — Indicate that a definition query on join table will effectively result in an inner join in ArcGIS Pro Ideas</title>
    <link>https://community.esri.com/t5/arcgis-pro-ideas/add-join-indicate-that-a-definition-query-on-join/idi-p/1385290</link>
    <description>&lt;P&gt;&lt;EM&gt;ArcGIS Pro 3.2.2&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;Background:&amp;nbsp;&lt;A href="https://community.esri.com/t5/arcgis-pro-questions/add-join-not-keeping-all-target-features/m-p/1385269/highlight/true#M79148" target="_self"&gt;Add Join not keeping all target features&lt;/A&gt;&lt;/P&gt;&lt;P&gt;When joining from tables A to B, if B has a definition query such as TYPE=100, then that definition query will effectively result in an inner join in the resulting AB join.&lt;/P&gt;&lt;P&gt;The Add Join tool says:&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;The join table has a definition query which will be applied to the input after performing the join.&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.esri.com/t5/arcgis-pro-ideas/add-join-should-warn-user-if-join-table-has-a/idi-p/1239925/highlight/true" target="_self"&gt;Add Join should warn user if join table has a definition query&lt;/A&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;That's helpful. But I wonder if it would be even more helpful to say that the definition query will effectively result in a matches-only join, even if "Keep all input records" is checked.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Bud_0-1708580612318.png" style="width: 999px;"&gt;&lt;img src="https://community.esri.com/t5/image/serverpage/image-id/95461iDAFEC9F33C1BC2F4/image-size/large?v=v2&amp;amp;px=999" role="button" title="Bud_0-1708580612318.png" alt="Bud_0-1708580612318.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Result:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Bud_1-1708586413591.png" style="width: 999px;"&gt;&lt;img src="https://community.esri.com/t5/image/serverpage/image-id/95469i7D5CB2506E8C92D9/image-size/large?v=v2&amp;amp;px=999" role="button" title="Bud_1-1708586413591.png" alt="Bud_1-1708586413591.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Users are often confused when a join table definition query excludes rows from the resulting join. Or worse, the user doesn't notice and produces incorrect results.&lt;/P&gt;&lt;P&gt;It's a common issue.&amp;nbsp;&lt;SPAN&gt;So I'm wondering if anything more can be done to prevent it.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Related:&lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;Data Management Ideas -&amp;nbsp;&lt;A href="https://community.esri.com/t5/data-management-ideas/honor-definition-query-when-joining-feature/idi-p/924590/highlight/true" target="_self"&gt;Honor Definition Query When Joining Feature Classes&lt;/A&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;ArcGIS Pro Ideas (Closed) -&amp;nbsp;&lt;A href="https://community.esri.com/t5/arcgis-pro-ideas/honor-definition-query-when-joining-feature/idi-p/957673/highlight/true" target="_self"&gt;Honor Definition Query When Joining Feature Classes&lt;/A&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;Bug -&amp;nbsp;Article ID:000007166 -&amp;nbsp;&lt;A href="https://support.esri.com/en-us/knowledge-base/open-attribute-table-returns-no-values-on-a-geodatabase-000007166" target="_self"&gt;Open Attribute Table returns no values on a geodatabase point feature class with a join and a definition query based on a joined field&lt;/A&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;BUG-000153808&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://support.esri.com/en-us/bug/the-add-join-tool-does-not-correctly-honor-the-definiti-bug-000153808" target="_self"&gt;The Add Join tool does not correctly honor the definition query on the join table.&lt;/A&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;BUG-000131999&lt;/SPAN&gt;&amp;nbsp;&lt;A href="https://support.esri.com/en-us/bug/definition-query-not-working-as-expected-in-a-joined-fe-bug-000131999" target="_self"&gt;Definition query not working as expected in a joined feature layer.&lt;/A&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;BUG-000129607&lt;/SPAN&gt;&amp;nbsp;&lt;A href="https://support.esri.com/en-us/bug/add-join-does-not-correctly-honor-definition-query-on-j-bug-000129607" target="_self"&gt;Add Join does not correctly honor definition query on join table.&lt;/A&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;BUG-000153950&lt;/SPAN&gt;&amp;nbsp;&lt;A href="https://support.esri.com/en-us/bug/in-arcgis-pro-when-adding-a-join-the-keep-all-target-fe-bug-000153950" target="_self"&gt;In ArcGIS Pro, when adding a join, the Keep All Target Features option is not honored if the joined table has a definition query applied to it.&lt;/A&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;BUG-000164109&lt;/SPAN&gt;&amp;nbsp;&lt;A href="https://support.esri.com/en-us/bug/exported-output-is-not-the-same-when-involving-definiti-bug-000164109" target="_self"&gt;&lt;SPAN&gt;Exported output is not the same when involving definition queries and join processes.&lt;/SPAN&gt;&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sat, 24 Feb 2024 16:04:52 GMT</pubDate>
    <dc:creator>Bud</dc:creator>
    <dc:date>2024-02-24T16:04:52Z</dc:date>
    <item>
      <title>Add Join — Indicate that a definition query on join table will effectively result in an inner join</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/add-join-indicate-that-a-definition-query-on-join/idi-p/1385290</link>
      <description>&lt;P&gt;&lt;EM&gt;ArcGIS Pro 3.2.2&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;Background:&amp;nbsp;&lt;A href="https://community.esri.com/t5/arcgis-pro-questions/add-join-not-keeping-all-target-features/m-p/1385269/highlight/true#M79148" target="_self"&gt;Add Join not keeping all target features&lt;/A&gt;&lt;/P&gt;&lt;P&gt;When joining from tables A to B, if B has a definition query such as TYPE=100, then that definition query will effectively result in an inner join in the resulting AB join.&lt;/P&gt;&lt;P&gt;The Add Join tool says:&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;The join table has a definition query which will be applied to the input after performing the join.&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.esri.com/t5/arcgis-pro-ideas/add-join-should-warn-user-if-join-table-has-a/idi-p/1239925/highlight/true" target="_self"&gt;Add Join should warn user if join table has a definition query&lt;/A&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;That's helpful. But I wonder if it would be even more helpful to say that the definition query will effectively result in a matches-only join, even if "Keep all input records" is checked.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Bud_0-1708580612318.png" style="width: 999px;"&gt;&lt;img src="https://community.esri.com/t5/image/serverpage/image-id/95461iDAFEC9F33C1BC2F4/image-size/large?v=v2&amp;amp;px=999" role="button" title="Bud_0-1708580612318.png" alt="Bud_0-1708580612318.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Result:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Bud_1-1708586413591.png" style="width: 999px;"&gt;&lt;img src="https://community.esri.com/t5/image/serverpage/image-id/95469i7D5CB2506E8C92D9/image-size/large?v=v2&amp;amp;px=999" role="button" title="Bud_1-1708586413591.png" alt="Bud_1-1708586413591.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Users are often confused when a join table definition query excludes rows from the resulting join. Or worse, the user doesn't notice and produces incorrect results.&lt;/P&gt;&lt;P&gt;It's a common issue.&amp;nbsp;&lt;SPAN&gt;So I'm wondering if anything more can be done to prevent it.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Related:&lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;Data Management Ideas -&amp;nbsp;&lt;A href="https://community.esri.com/t5/data-management-ideas/honor-definition-query-when-joining-feature/idi-p/924590/highlight/true" target="_self"&gt;Honor Definition Query When Joining Feature Classes&lt;/A&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;ArcGIS Pro Ideas (Closed) -&amp;nbsp;&lt;A href="https://community.esri.com/t5/arcgis-pro-ideas/honor-definition-query-when-joining-feature/idi-p/957673/highlight/true" target="_self"&gt;Honor Definition Query When Joining Feature Classes&lt;/A&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;Bug -&amp;nbsp;Article ID:000007166 -&amp;nbsp;&lt;A href="https://support.esri.com/en-us/knowledge-base/open-attribute-table-returns-no-values-on-a-geodatabase-000007166" target="_self"&gt;Open Attribute Table returns no values on a geodatabase point feature class with a join and a definition query based on a joined field&lt;/A&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;BUG-000153808&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://support.esri.com/en-us/bug/the-add-join-tool-does-not-correctly-honor-the-definiti-bug-000153808" target="_self"&gt;The Add Join tool does not correctly honor the definition query on the join table.&lt;/A&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;BUG-000131999&lt;/SPAN&gt;&amp;nbsp;&lt;A href="https://support.esri.com/en-us/bug/definition-query-not-working-as-expected-in-a-joined-fe-bug-000131999" target="_self"&gt;Definition query not working as expected in a joined feature layer.&lt;/A&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;BUG-000129607&lt;/SPAN&gt;&amp;nbsp;&lt;A href="https://support.esri.com/en-us/bug/add-join-does-not-correctly-honor-definition-query-on-j-bug-000129607" target="_self"&gt;Add Join does not correctly honor definition query on join table.&lt;/A&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;BUG-000153950&lt;/SPAN&gt;&amp;nbsp;&lt;A href="https://support.esri.com/en-us/bug/in-arcgis-pro-when-adding-a-join-the-keep-all-target-fe-bug-000153950" target="_self"&gt;In ArcGIS Pro, when adding a join, the Keep All Target Features option is not honored if the joined table has a definition query applied to it.&lt;/A&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;BUG-000164109&lt;/SPAN&gt;&amp;nbsp;&lt;A href="https://support.esri.com/en-us/bug/exported-output-is-not-the-same-when-involving-definiti-bug-000164109" target="_self"&gt;&lt;SPAN&gt;Exported output is not the same when involving definition queries and join processes.&lt;/SPAN&gt;&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 24 Feb 2024 16:04:52 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/add-join-indicate-that-a-definition-query-on-join/idi-p/1385290</guid>
      <dc:creator>Bud</dc:creator>
      <dc:date>2024-02-24T16:04:52Z</dc:date>
    </item>
    <item>
      <title>Re: Add Join — Indicate that a definition query on join table will effectively result in an inner join</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/add-join-indicate-that-a-definition-query-on-join/idc-p/1517873#M31501</link>
      <description>&lt;P&gt;Idea -&amp;nbsp;&lt;A href="https://community.esri.com/t5/arcgis-pro-ideas/add-join-create-independent-definition-query-on/idi-p/1385518" target="_self"&gt;Add Join — Create independent definition query on join table (pre-filter)&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 10 Aug 2024 14:23:32 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/add-join-indicate-that-a-definition-query-on-join/idc-p/1517873#M31501</guid>
      <dc:creator>Bud</dc:creator>
      <dc:date>2024-08-10T14:23:32Z</dc:date>
    </item>
    <item>
      <title>Re: Add Join — Indicate that a definition query on join table will effectively result in an inner join</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/add-join-indicate-that-a-definition-query-on-join/idc-p/1528419#M31826</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;P&gt;If the join table has a definition query, the &lt;SPAN class=""&gt;Keep all input records&lt;/SPAN&gt; parameter will have no effect. Manually updating the definition query by appending &lt;SPAN class=""&gt;or OBJECTID is null&lt;/SPAN&gt; can fix this if appropriate.&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;A href="https://pro.arcgis.com/en/pro-app/latest/tool-reference/data-management/add-join.htm" target="_blank" rel="noopener"&gt;https://pro.arcgis.com/en/pro-app/latest/tool-reference/data-management/add-join.htm&lt;/A&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 28 Aug 2024 05:53:21 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/add-join-indicate-that-a-definition-query-on-join/idc-p/1528419#M31826</guid>
      <dc:creator>Bud</dc:creator>
      <dc:date>2024-08-28T05:53:21Z</dc:date>
    </item>
  </channel>
</rss>

