<?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: GISOBJID for Hexagon EAM in Geoprocessing Questions</title>
    <link>https://community.esri.com/t5/geoprocessing-questions/gisobjid-for-hexagon-eam/m-p/1634529#M27606</link>
    <description>&lt;P&gt;Hey&amp;nbsp;&lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/551387"&gt;@rami_shah&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If possible, you may have better luck using the GLOBALID instead of the OBJECTID or GISOBJID you're mentioning. The reason is because the OBJECTID at least is a start at 0 and increment by 1 unique value, which will 100% have duplicates between layers. The GLOBALID is a GUID which is a 128 bit text string that is randomized, the chances of duplicates are astronomically low, and with around 200 million features we have not had a duplicate. These would then not overlap as there is such a low chance of one being reused, so this issue would inherently be out of worry.&lt;/P&gt;&lt;P&gt;I would personally use that, but if you're required to use OBJECTID or similar long integer types, then ESRI has safeguards into stopping duplication by using unique keys on a single table, to prevent overlap, you may want to assign ranges, like 1-100000 and 200000-300000 for the IDs for example, so they don't have a chance to overlap, so start at 1 and start at 200000, so on, but the GLOBALID method will solve itself!&lt;/P&gt;&lt;P&gt;Cody&lt;/P&gt;</description>
    <pubDate>Mon, 21 Jul 2025 12:56:43 GMT</pubDate>
    <dc:creator>CodyPatterson</dc:creator>
    <dc:date>2025-07-21T12:56:43Z</dc:date>
    <item>
      <title>GISOBJID for Hexagon EAM</title>
      <link>https://community.esri.com/t5/geoprocessing-questions/gisobjid-for-hexagon-eam/m-p/1634513#M27605</link>
      <description>&lt;P&gt;Hello experts,&lt;/P&gt;&lt;P&gt;I am integrating GIS with EAM (enterprise asset mgmt). I need to match unique identifier aka GISID. Does Esri have built in option to keep track of new and existing&amp;nbsp;GISID.&lt;/P&gt;&lt;P&gt;1. I want to ensure it is not duplicated&lt;/P&gt;&lt;P&gt;2. group 1 doesn't overlap with group 2 and vice versa&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Note:&amp;nbsp;GISID is a field in gis database with long integer type. thanks in advance for your help!&lt;/P&gt;&lt;P&gt;R&lt;/P&gt;</description>
      <pubDate>Wed, 23 Jul 2025 12:00:08 GMT</pubDate>
      <guid>https://community.esri.com/t5/geoprocessing-questions/gisobjid-for-hexagon-eam/m-p/1634513#M27605</guid>
      <dc:creator>rami_shah</dc:creator>
      <dc:date>2025-07-23T12:00:08Z</dc:date>
    </item>
    <item>
      <title>Re: GISOBJID for Hexagon EAM</title>
      <link>https://community.esri.com/t5/geoprocessing-questions/gisobjid-for-hexagon-eam/m-p/1634529#M27606</link>
      <description>&lt;P&gt;Hey&amp;nbsp;&lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/551387"&gt;@rami_shah&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If possible, you may have better luck using the GLOBALID instead of the OBJECTID or GISOBJID you're mentioning. The reason is because the OBJECTID at least is a start at 0 and increment by 1 unique value, which will 100% have duplicates between layers. The GLOBALID is a GUID which is a 128 bit text string that is randomized, the chances of duplicates are astronomically low, and with around 200 million features we have not had a duplicate. These would then not overlap as there is such a low chance of one being reused, so this issue would inherently be out of worry.&lt;/P&gt;&lt;P&gt;I would personally use that, but if you're required to use OBJECTID or similar long integer types, then ESRI has safeguards into stopping duplication by using unique keys on a single table, to prevent overlap, you may want to assign ranges, like 1-100000 and 200000-300000 for the IDs for example, so they don't have a chance to overlap, so start at 1 and start at 200000, so on, but the GLOBALID method will solve itself!&lt;/P&gt;&lt;P&gt;Cody&lt;/P&gt;</description>
      <pubDate>Mon, 21 Jul 2025 12:56:43 GMT</pubDate>
      <guid>https://community.esri.com/t5/geoprocessing-questions/gisobjid-for-hexagon-eam/m-p/1634529#M27606</guid>
      <dc:creator>CodyPatterson</dc:creator>
      <dc:date>2025-07-21T12:56:43Z</dc:date>
    </item>
  </channel>
</rss>

