SalesLogix web client error: The configuration map for IAccount is not defined. please See your system administrator

In the SalesLogix web client when searching for duplicates, the Speedsearch Indexes PMI:Account, PMI:Contact, and PMI:Lead are used to search for duplicates.  The web also has a “definition” configuration file that essentially maps the Speedsearch index attributes to the corresponding entity model properties.  This information is stored in a filed called PotentialMatchConfiguration.xml in the VFS.  This file is in the config portion of the VFS, not the model.  The exact path of the file is ConfigurationGlobalPotentialMatchConfiguration.xml. Because this file exists in the config area it is usually not affected by upgrades. 

You can access this area via the Application Architect using the Virtual File System Explorer (Cntrl+Alt+F).

If you examine the file you can see its structure:

<?xml version=”1.0″?>
<PotentialMatchConfiguration>
  <EntityMaps>
    <MatchEntityIndexMap Name=”ILead” EntityType=”Sage.Entity.Interfaces.ILead, Sage.Entity.Interfaces, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null”>
      <DisplayName><![CDATA[Lead enitiy to index map.]]></DisplayName>
      <PropertyMaps>
        <MatchPropertyFilterMap PropertyName=”FirstName” DisplayOrder=”1″ Enabled=”False” Required=”False”>
          <DisplayName><![CDATA[First Name]]></DisplayName>
          <IndexFilterMaps>
            <MatchIndexFilterMap IndexName=”PMI.Lead” FilterName=”Lead.FirstName” PropertyName=”FirstName” EntityType=”Sage.Entity.Interfaces.ILead, Sage.Entity.Interfaces, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null” />
            <MatchIndexFilterMap IndexName=”PMI.Contact” FilterName=”Contact.Firstname” PropertyName=”FirstName” EntityType=”Sage.Entity.Interfaces.IContact, Sage.Entity.Interfaces, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null” />
          </IndexFilterMaps>
        </MatchPropertyFilterMap>
        <MatchPropertyFilterMap PropertyName=”LastName” DisplayOrder=”2″ Enabled=”False” Required=”True”>
          <DisplayName><![CDATA[Last Name]]></DisplayName>
          <IndexFilterMaps>
            <MatchIndexFilterMap IndexName=”PMI.Lead” FilterName=”Lead.LastName” PropertyName=”LastName” EntityType=”Sage.Entity.Interfaces.ILead, Sage.Entity.Interfaces, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null” />
            <MatchIndexFilterMap IndexName=”PMI.Contact” FilterName=”Contact.Lastname” PropertyName=”LastName” EntityType=”Sage.Entity.Interfaces.IContact, Sage.Entity.Interfaces, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null” />
          </IndexFilterMaps>
        </MatchPropertyFilterMap>

Shown above is just the starting portion of the XML.  There should be 3 MatchEntityIndexMap definitions in the file with names of ILead, IContact, and IAccount.  If you receive the error similar to

The configuration map for IAccount is not defined.  please See your system administrator

This is because this XML file is missing the XML definition for that particular MatchEntityIndexMap. 

To fix this problem what you can do is to right click on the xml file in the VFS Explorer in Application Architect and choose delete.  You will then need to do an IISReset on the web server.  Then the next time a user attempts to access the duplicate merge functionality the XML file will be re-generated correctly and the error should go away.

Note I have run into situations where XML files do not show under the VFS Explorer due to data issues with the record in the VIRTUALFILESYSTEM table as it relates to their parent objects.  If you do not see the PotentialMatchConfiguration.xml file in the VFS Explorer you can always access it via SQL using this statement:

select * from virtualfilesystem where itemname = ‘potentialmatchconfiguration.xml’

To remove the XML from the VFS you can use:

delete from virtualfilesystem where itemname = ‘potentialmatchconfiguration.xml’

You will still need to do an IISReset after running the delete command in SQL.

Also note that the Application Architect does not properly refresh the VFS explorer as you would expect.  After the XML file is regenerated, you will not see it in the VFS Explorer (even if you right click and choose refresh) until you close Application Architect and log back in.