VERIFIED SOLUTION i
X

Custom indexing not working as expected in EngageOne Vault

Issue

Custom indexes not being created as expected in EngageOne® Vault

Cause

User has simply added additional parameters to the document record journal being loaded into Vault:

D|ABCDE12345|20181031|11|Tyrion Lanister|Kings Landing Westeros|999|0123456789|Sample1|

Resolution

UPDATED: December 3, 2018


The document record in a flat journal can only contain the information for the default Vault parameters:

D|CustId|Date|PageCount|CustName|CustAddr|

If additional indexes are required, these need to added via an Attribute as follows (to appear before the document record in the journal):

A|messagenumber|999|
A|campaignnumber|0123456789|
A|samplenumber|Sample1|

The relevant entry in the filemap in profiles.ini would be as follows:

Indexn=messagenumber,messagenumber,dh,Message Number Value
Indexn=campaignnumber,campaignnumber,dh,Campaign Number Value
Indexn=samplenumberr,samplenumber,dh,Sample Number Value

* Note, the index numbers must be sequential, you cannot miss index numbers in the index definition, for example:

Index1=
Index2=
Index3=
Index4=
Index6=

The attribute value immediately after the A| record comes from the second field in the index setting, and should be in lower case.

The last value shown in the index entry is the one used for searching in the render engine when connected to the relevant database.

The customindexing parameter also has to be active in the relevant profile:

customindexing=1

 

Environment Details

Product Feature: Loader
 

Downloads

  • No Downloads