<?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 Defining a Composite in 10.0 your Search Fields Don't Match? in Data Management Questions</title>
    <link>https://community.esri.com/t5/data-management-questions/defining-a-composite-in-10-0-your-search-fields/m-p/555573#M31483</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I am trying to automate the creation/update of several geocoders into Composites and have a couple things that are not nice that I wonder if anyone has worked out.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;UL&gt;&lt;BR /&gt;&lt;LI&gt;In the Locator XML file, you can define you want the X/Y values written, but when setting a composite to use several locators that have this setting defined it doesn't carry them through.&lt;/LI&gt;&lt;BR /&gt;&lt;LI&gt;In the Locator XML file, you can define alternate field names to trigger on, but when setting a composite to use several locators that have this setting defined it doesn't carry them through forcing you to go through and manually enter these all over again.&lt;/LI&gt;&lt;BR /&gt;&lt;/UL&gt;&lt;BR /&gt;&lt;SPAN&gt;Is there a place where you can define Presets for the new Composite Locator build process to address these? For me moving to 10.1 isn't a option since so much was changed on the Server and ArcObjects level we need more time to migrate.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Suggestions???&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 01 Mar 2013 16:17:43 GMT</pubDate>
    <dc:creator>DEWright_CA</dc:creator>
    <dc:date>2013-03-01T16:17:43Z</dc:date>
    <item>
      <title>Defining a Composite in 10.0 your Search Fields Don't Match?</title>
      <link>https://community.esri.com/t5/data-management-questions/defining-a-composite-in-10-0-your-search-fields/m-p/555573#M31483</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I am trying to automate the creation/update of several geocoders into Composites and have a couple things that are not nice that I wonder if anyone has worked out.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;UL&gt;&lt;BR /&gt;&lt;LI&gt;In the Locator XML file, you can define you want the X/Y values written, but when setting a composite to use several locators that have this setting defined it doesn't carry them through.&lt;/LI&gt;&lt;BR /&gt;&lt;LI&gt;In the Locator XML file, you can define alternate field names to trigger on, but when setting a composite to use several locators that have this setting defined it doesn't carry them through forcing you to go through and manually enter these all over again.&lt;/LI&gt;&lt;BR /&gt;&lt;/UL&gt;&lt;BR /&gt;&lt;SPAN&gt;Is there a place where you can define Presets for the new Composite Locator build process to address these? For me moving to 10.1 isn't a option since so much was changed on the Server and ArcObjects level we need more time to migrate.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Suggestions???&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Mar 2013 16:17:43 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/defining-a-composite-in-10-0-your-search-fields/m-p/555573#M31483</guid>
      <dc:creator>DEWright_CA</dc:creator>
      <dc:date>2013-03-01T16:17:43Z</dc:date>
    </item>
  </channel>
</rss>

