<?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: Invalid Terminal Configuration error at 2.3 in Gas and Pipeline Questions</title>
    <link>https://community.esri.com/t5/gas-and-pipeline-questions/invalid-terminal-configuration-error-at-2-3/m-p/586401#M440</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I don't populate a value.&amp;nbsp; Do I need to change that to "Default" now for all single terminal devices?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 30 Jan 2019 16:58:29 GMT</pubDate>
    <dc:creator>MarkCederholm</dc:creator>
    <dc:date>2019-01-30T16:58:29Z</dc:date>
    <item>
      <title>Invalid Terminal Configuration error at 2.3</title>
      <link>https://community.esri.com/t5/gas-and-pipeline-questions/invalid-terminal-configuration-error-at-2-3/m-p/586399#M438</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;My network configuration (based on UPDM) which worked fine at 2.2 is failing at 2.3.&amp;nbsp; My customer meters are at the default single terminal configuration, and when I enable topology, every single meter gets error type 39 "Point feature has invalid terminal configuration".&amp;nbsp; Has anyone else seen this issue?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Jan 2019 16:43:53 GMT</pubDate>
      <guid>https://community.esri.com/t5/gas-and-pipeline-questions/invalid-terminal-configuration-error-at-2-3/m-p/586399#M438</guid>
      <dc:creator>MarkCederholm</dc:creator>
      <dc:date>2019-01-30T16:43:53Z</dc:date>
    </item>
    <item>
      <title>Re: Invalid Terminal Configuration error at 2.3</title>
      <link>https://community.esri.com/t5/gas-and-pipeline-questions/invalid-terminal-configuration-error-at-2-3/m-p/586400#M439</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Error 39 means the terminal path is invalid.&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="https://pro.arcgis.com/en/pro-app/help/data/utility-network/manage-error-features.htm" title="https://pro.arcgis.com/en/pro-app/help/data/utility-network/manage-error-features.htm"&gt;Error feature management—ArcGIS Pro | ArcGIS Desktop&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What values do you see in Terminal path?&lt;/P&gt;&lt;P&gt;&lt;IMG class="image-1 jive-image" src="https://community.esri.com/legacyfs/online/436158_pastedImage_2.png" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Jan 2019 16:54:11 GMT</pubDate>
      <guid>https://community.esri.com/t5/gas-and-pipeline-questions/invalid-terminal-configuration-error-at-2-3/m-p/586400#M439</guid>
      <dc:creator>PaulLeBlanc1</dc:creator>
      <dc:date>2019-01-30T16:54:11Z</dc:date>
    </item>
    <item>
      <title>Re: Invalid Terminal Configuration error at 2.3</title>
      <link>https://community.esri.com/t5/gas-and-pipeline-questions/invalid-terminal-configuration-error-at-2-3/m-p/586401#M440</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I don't populate a value.&amp;nbsp; Do I need to change that to "Default" now for all single terminal devices?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Jan 2019 16:58:29 GMT</pubDate>
      <guid>https://community.esri.com/t5/gas-and-pipeline-questions/invalid-terminal-configuration-error-at-2-3/m-p/586401#M440</guid>
      <dc:creator>MarkCederholm</dc:creator>
      <dc:date>2019-01-30T16:58:29Z</dc:date>
    </item>
    <item>
      <title>Re: Invalid Terminal Configuration error at 2.3</title>
      <link>https://community.esri.com/t5/gas-and-pipeline-questions/invalid-terminal-configuration-error-at-2-3/m-p/586402#M441</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This might be the issue: I create connectivity associations between each meter and a junction so that I can have multiple meters per assembly.&amp;nbsp; Here's an example of an association record that I import:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ASSOCIATIONTYPE,FROMFEATURECLASS,FROMASSETGROUP,FROMASSETTYPE,FROMGLOBALID,FROMTERMINAL,TOFEATURECLASS,TOASSETGROUP,TOASSETTYPE,TOGLOBALID,TOTERMINAL,ISCONTENTVISIBLE&lt;BR /&gt;Junction Junction Connectivity,PipelineDevice,Meter,Customer,{31C37CF7-CF62-4700-BB1D-90EDEC05F4FD},Single Terminal,PipelineJunction,Connection Point,Riser Connection,{06AD49ED-BE80-4DC5-ACD5-C28436EC0DC4},Single Terminal,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there something I need to change?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Jan 2019 17:21:24 GMT</pubDate>
      <guid>https://community.esri.com/t5/gas-and-pipeline-questions/invalid-terminal-configuration-error-at-2-3/m-p/586402#M441</guid>
      <dc:creator>MarkCederholm</dc:creator>
      <dc:date>2019-01-30T17:21:24Z</dc:date>
    </item>
    <item>
      <title>Re: Invalid Terminal Configuration error at 2.3</title>
      <link>https://community.esri.com/t5/gas-and-pipeline-questions/invalid-terminal-configuration-error-at-2-3/m-p/586403#M442</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Well the default value for the field is 'Default', so it should be populated.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Jan 2019 17:43:13 GMT</pubDate>
      <guid>https://community.esri.com/t5/gas-and-pipeline-questions/invalid-terminal-configuration-error-at-2-3/m-p/586403#M442</guid>
      <dc:creator>PaulLeBlanc1</dc:creator>
      <dc:date>2019-01-30T17:43:13Z</dc:date>
    </item>
    <item>
      <title>Re: Invalid Terminal Configuration error at 2.3</title>
      <link>https://community.esri.com/t5/gas-and-pipeline-questions/invalid-terminal-configuration-error-at-2-3/m-p/586404#M443</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;OK, I'll update my script to see if that fixes things.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Jan 2019 17:48:21 GMT</pubDate>
      <guid>https://community.esri.com/t5/gas-and-pipeline-questions/invalid-terminal-configuration-error-at-2-3/m-p/586404#M443</guid>
      <dc:creator>MarkCederholm</dc:creator>
      <dc:date>2019-01-30T17:48:21Z</dc:date>
    </item>
    <item>
      <title>Re: Invalid Terminal Configuration error at 2.3</title>
      <link>https://community.esri.com/t5/gas-and-pipeline-questions/invalid-terminal-configuration-error-at-2-3/m-p/586405#M444</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;That did the trick, thanks.&amp;nbsp; I'm surprised the default value wasn't automatically&amp;nbsp;filled when I populated the asset package.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Jan 2019 19:22:14 GMT</pubDate>
      <guid>https://community.esri.com/t5/gas-and-pipeline-questions/invalid-terminal-configuration-error-at-2-3/m-p/586405#M444</guid>
      <dc:creator>MarkCederholm</dc:creator>
      <dc:date>2019-01-30T19:22:14Z</dc:date>
    </item>
  </channel>
</rss>

