How do I convert a hub XML from matching to lookup mode?

 

If you've built a process in Cortex, you can export the settings XML and start using it with our precompiled batch scripts immediately, although if you are planning to utilize lookup mode there are some additional steps outlined below to follow.

 

Make a copy of the xml and then edit the copy so that you can always go back to the original if you make a mistake.


1) Change mode from matching to lookup
<mode>lookup</mode>

 

2) Change opening and closing <matching> tags to <lookup>
*note this is case sensitive, do not use Lookup


3) Remove allowBlankKeys node and dynamicKeys
<allowBlankKeys>false</allowBlankKeys>
<dynamicKeys>false</dynamicKeys>


4) Remove certain output options
<outputHeader enabled="true" />
<outputHighestScores enabled="false" />
<outputDuplicatesCount enabled="false" />
<outputBestMatchesOnly enabled="false" />
<outputLargeClusters enabled="false" records="false" />
<outputCompareResults enabled="false" />

 

*Note - you can still leave in the following output options, so still leave the options node

These will stay:
<options>
<outputUniqueRefsOnly enabled="false" />
<outputComponentScores enabled="false" />
<outputExactMatchScores enabled="false" />
<outputAllExactMatches enabled="false" />
</options>


5) Remove output types - including the opening and closing types tag as well

<types>
<matchingPairs enabled="true" />
<groupedMatchingPairs enabled="false" />
<matchingGroups enabled="true" />
<dedupedData enabled="false" />
<duplicateData enabled="false" />
<matchedData enabled="false" />
</types>

 

6) Remove bridging prevention and the options node below it.

<bridgingPrevention>
<nameBridgingPrevention enabled="false" />
<prefixBridgingPrevention enabled="false" />
<companyBridgingPrevention enabled="false" />
<aggressiveSplitting enabled="false" />
<masterRecordIdentification enabled="false" />
</bridgingPrevention>
<options>
<outputDeletedMatches enabled="false" />
<outputSubRecords enabled="false" />
</options>

 

7) and remove the bestFitMethods and volume if they're there - normally located after the post matching rules, these are in newer versions of hub, and not applicable to lookup mode.


<bestFitMethods enabled="false" />
<volume>4</volume>

 

You now should have successfully converted the xml to lookup mode, normally the easiest way to test is to use the demo client to apply the settings and if the engine status changes to Ready then you should be good, if the engine state stays at initialized - that would indicate there's still an issue with your xml.

 

 

 

 

Was this article helpful?
0 out of 0 found this helpful

have a question or not finding what you're looking for?

Submit a ticket to get some help