<?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 Symbolizing features based on related records using branch versioned data   in Geodatabase Questions</title>
    <link>https://community.esri.com/t5/geodatabase-questions/symbolizing-features-based-on-related-records/m-p/792200#M2172</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;DIV&gt;I have a tree feature class with a one to many relationship to an inspection table in a SDE database. With traditional versioning I am able to create a query layer showing the most recent inspection, publishing this to Portal for ArcGIS and symbolizing the tree condition. I switched to branch version and realized that I can't do&amp;nbsp;SQL queries anymore, however symbolizing the trees based on the last entry in the related table is crucial to the workflow. I am wondering if there is any other way to accomplish this or do I need to go back to traditional versioning &lt;A href="https://community.esri.com/migrated-users/2621"&gt;George Thompson&lt;/A&gt;&amp;nbsp;If I have to go back to traditional versioning what are the steps to built back?&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;Searching "query related records on feature service" ArcGIS REST API comes up a lot - maybe that's the way to go?&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;Thanks a lot,&lt;/DIV&gt;&lt;DIV&gt;Doreen&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 03 Nov 2020 15:00:16 GMT</pubDate>
    <dc:creator>DoreenGroth</dc:creator>
    <dc:date>2020-11-03T15:00:16Z</dc:date>
    <item>
      <title>Symbolizing features based on related records using branch versioned data</title>
      <link>https://community.esri.com/t5/geodatabase-questions/symbolizing-features-based-on-related-records/m-p/792200#M2172</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;DIV&gt;I have a tree feature class with a one to many relationship to an inspection table in a SDE database. With traditional versioning I am able to create a query layer showing the most recent inspection, publishing this to Portal for ArcGIS and symbolizing the tree condition. I switched to branch version and realized that I can't do&amp;nbsp;SQL queries anymore, however symbolizing the trees based on the last entry in the related table is crucial to the workflow. I am wondering if there is any other way to accomplish this or do I need to go back to traditional versioning &lt;A href="https://community.esri.com/migrated-users/2621"&gt;George Thompson&lt;/A&gt;&amp;nbsp;If I have to go back to traditional versioning what are the steps to built back?&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;Searching "query related records on feature service" ArcGIS REST API comes up a lot - maybe that's the way to go?&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;Thanks a lot,&lt;/DIV&gt;&lt;DIV&gt;Doreen&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 Nov 2020 15:00:16 GMT</pubDate>
      <guid>https://community.esri.com/t5/geodatabase-questions/symbolizing-features-based-on-related-records/m-p/792200#M2172</guid>
      <dc:creator>DoreenGroth</dc:creator>
      <dc:date>2020-11-03T15:00:16Z</dc:date>
    </item>
    <item>
      <title>Re: Symbolizing features based on related records using branch versioned data </title>
      <link>https://community.esri.com/t5/geodatabase-questions/symbolizing-features-based-on-related-records/m-p/792201#M2173</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It looks like you can have a related table:&amp;nbsp;&lt;A class="link-titled" href="https://pro.arcgis.com/en/pro-app/help/data/geodatabases/overview/register-a-dataset-as-branch-versioned.htm" title="https://pro.arcgis.com/en/pro-app/help/data/geodatabases/overview/register-a-dataset-as-branch-versioned.htm"&gt;Register a dataset as branch versioned—ArcGIS Pro | Documentation&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;BLOCKQUOTE class="jive_macro_quote jive-quote jive_text_macro"&gt;&lt;UL style="color: #4c4c4c; background-color: #ffffff; font-size: 0.9375rem; margin-left: 0.775rem; margin-top: 0px; margin-bottom: 1.55rem; padding: 0px;"&gt;&lt;LI style="margin: 0.3875rem 0px 0.3875rem 1.5rem;"&gt;For datasets participating in relationship classes, the primary key of the relationship must not use the Object ID field. For more information, see&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://pro.arcgis.com/en/pro-app/help/data/relationships/relationship-class-properties.htm" style="color: #0074b8; text-decoration: none;"&gt;Relationship class properties&lt;/A&gt;.&lt;/LI&gt;&lt;/UL&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am not sure about symbolizing on the related table from the branch versioned layers.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you go back to traditional versioning, you would need to&amp;nbsp;&lt;A class="link-titled" href="https://pro.arcgis.com/en/pro-app/help/data/geodatabases/overview/reconcile-and-post-edits-to-a-branch-version.htm" title="https://pro.arcgis.com/en/pro-app/help/data/geodatabases/overview/reconcile-and-post-edits-to-a-branch-version.htm"&gt;Reconcile and post edits to a branch version—ArcGIS Pro | Documentation&lt;/A&gt;, delete all the branch versions (not DEFAULT)&amp;nbsp;then unregister as branch versioned then follow the traditional workflows.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have NOT tested these workflows out: moving from branch --&amp;gt; traditional versioning, using REST API for related data&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would also recommend testing this in a DEV environment before making changes in a PROD system.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 Nov 2020 16:09:08 GMT</pubDate>
      <guid>https://community.esri.com/t5/geodatabase-questions/symbolizing-features-based-on-related-records/m-p/792201#M2173</guid>
      <dc:creator>George_Thompson</dc:creator>
      <dc:date>2020-11-03T16:09:08Z</dc:date>
    </item>
    <item>
      <title>Re: Symbolizing features based on related records using branch versioned data</title>
      <link>https://community.esri.com/t5/geodatabase-questions/symbolizing-features-based-on-related-records/m-p/792202#M2174</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks &lt;A href="https://community.esri.com/migrated-users/2621"&gt;George Thompson&lt;/A&gt;‌ for your quick response. I decided to stick with branch versioning, and using python to symbolize my data might be&amp;nbsp;the&amp;nbsp;only&amp;nbsp;option I have right now. However, I think that's a little much for a basic GIS task.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.esri.com/community/gis/web-gis/arcgisonline/blog/2020/03/25/easy-how-to-symbology-using-related-records"&gt;https://community.esri.com/community/gis/web-gis/arcgisonline/blog/2020/03/25/easy-how-to-symbology-using-related-records&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 Nov 2020 19:20:13 GMT</pubDate>
      <guid>https://community.esri.com/t5/geodatabase-questions/symbolizing-features-based-on-related-records/m-p/792202#M2174</guid>
      <dc:creator>DoreenGroth</dc:creator>
      <dc:date>2020-11-03T19:20:13Z</dc:date>
    </item>
  </channel>
</rss>

