<?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 Attribute Assistant: Generate Same ID in two different tables in State &amp; Local Government Questions</title>
    <link>https://community.esri.com/t5/state-local-government-questions/attribute-assistant-generate-same-id-in-two/m-p/400659#M2456</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Is it possible to use the GENERATE_ID method to generate the same id into to two different tables?&amp;nbsp; I'm trying to piece together the logic in my head as to how it could work.&amp;nbsp; Here is my situation:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I create point features that have names and I have&amp;nbsp; an alias table for those points, where the aliases are derivatives of those names.&amp;nbsp; I use this point feature class for geocoding with the aliases as the alt_names table.&amp;nbsp; Let's say I have a point and it's full name is:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;JACKSON ELEMENTARY SCHOOL&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That point would have at least two different aliases:&lt;/P&gt;&lt;P&gt;JACKSON ELEMENTARY&lt;/P&gt;&lt;P&gt;JACKSON&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What I'm after is a Join-Item between the proper name on the point and the alias records.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As I'm typing this out, I can already see a flaw in using the GENERATE_ID method for the aliases, because of the way the GENERATE ID sequence counter is incremented.&amp;nbsp; Perhaps the way to go would be to use the LAST_VALUE method referring back to the point attribute table, and the last generated id.&amp;nbsp; Thoughts?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 16 Aug 2016 15:08:31 GMT</pubDate>
    <dc:creator>JoeBorgione</dc:creator>
    <dc:date>2016-08-16T15:08:31Z</dc:date>
    <item>
      <title>Attribute Assistant: Generate Same ID in two different tables</title>
      <link>https://community.esri.com/t5/state-local-government-questions/attribute-assistant-generate-same-id-in-two/m-p/400659#M2456</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Is it possible to use the GENERATE_ID method to generate the same id into to two different tables?&amp;nbsp; I'm trying to piece together the logic in my head as to how it could work.&amp;nbsp; Here is my situation:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I create point features that have names and I have&amp;nbsp; an alias table for those points, where the aliases are derivatives of those names.&amp;nbsp; I use this point feature class for geocoding with the aliases as the alt_names table.&amp;nbsp; Let's say I have a point and it's full name is:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;JACKSON ELEMENTARY SCHOOL&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That point would have at least two different aliases:&lt;/P&gt;&lt;P&gt;JACKSON ELEMENTARY&lt;/P&gt;&lt;P&gt;JACKSON&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What I'm after is a Join-Item between the proper name on the point and the alias records.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As I'm typing this out, I can already see a flaw in using the GENERATE_ID method for the aliases, because of the way the GENERATE ID sequence counter is incremented.&amp;nbsp; Perhaps the way to go would be to use the LAST_VALUE method referring back to the point attribute table, and the last generated id.&amp;nbsp; Thoughts?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Aug 2016 15:08:31 GMT</pubDate>
      <guid>https://community.esri.com/t5/state-local-government-questions/attribute-assistant-generate-same-id-in-two/m-p/400659#M2456</guid>
      <dc:creator>JoeBorgione</dc:creator>
      <dc:date>2016-08-16T15:08:31Z</dc:date>
    </item>
    <item>
      <title>Re: Attribute Assistant: Generate Same ID in two different tables</title>
      <link>https://community.esri.com/t5/state-local-government-questions/attribute-assistant-generate-same-id-in-two/m-p/400660#M2457</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It looks like the LAST_VALUE method only looks that the current/active table, however LINK_TABLE_ASSET seems to do the trick. As I create a point I fill in the info needed and the GENERATE_ID method does it's thing.&amp;nbsp; With that new point still selected, I can create as many aliases as I like, and the generated id from the point populates the appropriate field in the alias table....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;added edit:&amp;nbsp; When using the GENERATE_ID for this particular purpose I set On Create = 1 along with Manual Only = 1.&amp;nbsp; I switched On Change (Attributes) as well as On Change (Geometry) to 0 (zero).&amp;nbsp; If you have&amp;nbsp; either of the the two 'change' fields non-zero, it'll increment that id for the point, and goof up the desired relationship between the point feature and the (related) alias table.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Aug 2016 15:44:33 GMT</pubDate>
      <guid>https://community.esri.com/t5/state-local-government-questions/attribute-assistant-generate-same-id-in-two/m-p/400660#M2457</guid>
      <dc:creator>JoeBorgione</dc:creator>
      <dc:date>2016-08-16T15:44:33Z</dc:date>
    </item>
  </channel>
</rss>

