mDesktop in Depth - Main File Layout

 

Summary

The best way to configure a Main File with all the fields required for processing your data file is to use the Setup Wizard.  If, for some reason this is not possible or not an appropriate option, this section explains the fields your Main File must have so that mDesktop can do what is required.

There are basically two kinds of fields that the system uses.  First, there are Input Fields.  These are the fields that you, the user, will supply for mDesktop's processing.  If they are name and address fields, you must give them standard mDesktop field names, because otherwise mDesktop will not recognize that it must apply appropriate processing to these fields.  For example, it must know if a field is a freeform field containing a person's name, or if it contains just the surname, or if it is an address line etc.  Although mDesktop can search through name fields for job titles, through address lines for names or zip codes etc., it will work much more effectively if you can label your data with appropriate mDesktop standard field names.

Additionally, mDesktop uses Generated Fields.  These are fields that probably weren't in your input data, but mDesktop will generate them from your data. They are critical to the main processing steps (deduplication etc).  It is normal to have the input fields at the start of your Main File layout, in one block, and to have the generated fields in another block at the end of the layout. We recommend that you keep to this unless you have a special reason not to, as this allows mDesktop to work out which fields are Input Fields and which are Generated.

However, as shown in mDesktop Field Names and Usage, some fields can be Input in one file but Generated in another.  Also, some Input fields can be replaced by Generated fields.

 

mDesktop Field Names and Usage

The table in Appendix A - Field Names & Usage  lists field names and usage in alphabetical order.  

Quality Assurance Field

mDesktop requires a FLAG field to prepare the Data Summary and for View Records by Category to allow you to examine certain categories of a record.  Entries in the Flag field are explained in Appendix B.

mDesktop Field names by Type

These are the main data fields that mDesktop recognizes specifically for import or matching:

Personal Name

  • ADDRESSEE, CONTACT, FORENAMES, FORENAMES2, INITIALS, INITIALS2, NAME, NAME1, NAME2, NAME3, NAME2FOUND, NAME_KEY, PREFIX, PREFIX2, QUAL, SALUTATION, SEX, SUFFIX, SURNAME, SURNAME2

Company Name

  • COMPANY, COY_KEY, COY_NAME, NAME1, NAME2, NAME3

Job

  • DEPARTMENT, JOB_TITLE

Address

  • ADDRESS1 to 9, ADD_KEY, COUNTY, COUNTRY, DPS, POSTCODE, POST_IN, POST_OUT, PREMISE, STATE, TOWN, ZIP

Telephone

  • FAX, REST_PHONE, STD_CODE, TELEPHONE

Campaign

  • MAILING_ID, MAIL_DATE

Match Set Grouping

  • MATCH_REF, SET_DUPS, OVERLAPREF, OVERLAPCNT, MATCHSCORE

Deletion Priority

  • DEL_PRI

Quality Assurance

  • FLAG

Unique Reference

  • UNIQUE_REF

 

Using Your Own Field Names

You may use your own field names within mDesktop.  If you do, mDesktop will not recognize them for special processing (e.g. if you name a field as CUSTOMER instead of ADDRESSEE, mDesktop will not apply its personal name processing to that field).  This is because mDesktop uses the field name as the main indicator to tell it what kind of data is likely to be in that field.

Although mDesktop won't apply any special processing to your own field names, it will apply its standard string handling routines.  This means that you can use any field you like as either a matching key or for matching weights. We don't recommend doing this until you are confident that you completely understand how mDesktop works, as using a non standard field can have a drastic effect on your matching results.

To allow you to use your own field names safely, we have set down a few guidelines on what to call your fields.  If you follow these rules, you should have no problems using your own fields in mDesktop:

  • Each field name in a Main File should be unique. If you have fields that do a similar thing, number them – for example, "CUSTOMER1", "CUSTOMER2" etc.
  • Whenever possible, select the field name "OTHER" from the suggested list in the Setup Wizard for fields that you know mDesktop won't need to know about.  We appreciate that in many situations, these names would not be sufficiently meaningful for processing, so in these cases, follow the naming rules below.
  • Field names must not be greater than 10 (ten) characters long
  • Field names must ONLY contain the letters A-Z or the numbers 0-9, or the underscore character ("_").  Field names must NOT contain spaces or any other kind of punctuation.
  • Field names must start with a letter (A-Z) NOT a number or an underscore.
  • Field names are not case sensitive, so 'CUSTNAME' is the same as 'CustName' or 'custname'
  • Field names must be AT LEAST three characters long.
  • Although you should follow these rules for your field NAMES, you can use different TYPES of fields (character, numeric, logical, date etc.).  However, mDesktop can only match on character fields.
  • Do not use any field names specified in the reserved list, as use of these names may conflict with mDesktop's operation.

Words Not To Use As Field Names

Words Not To Use As Field Names

Words Not To Use As Field Names

There follows a provisional list of "reserved names" in mDesktop.  It is not guaranteed to be complete, but the majority of names to avoid should be included.

 

ALL_RUNS            

AUTO_MACRO

AUTO_RUN            

BAG_MAIL            

BROW_PREF           

CBC_SORT            

CCBUFF              

CC_RET_VAL          

CFL_BAGPOS          

CFL_IND             

CFL_LAST            

CFL_OFFICE          

CLIENT              

CLOCK_STAT          

CLTFILE             

CNTY_LINE

CODE        

COMP_WARN

COUNT_IND           

CST_ITM             

CURRSOUNDS

CURRWORDS

CURR_DIR            

CURR_KEY            

CURR_NAME           

CURR_WIND           

DATABASE

DB_ALIAS            

DB_IN_USE           

FROM_FILE  

FRONT_DEMO

FULL_PCODE          

FUNNY_CASE          

GOOD_PATH           

HELPSTRING          

HIGH_IND            

HIGH_KEY            

HIGH_SCORE          

IDF_IND             

IMPORT_OPT          

INC_DPS             

INDEXBLOCK          

INDEX_NAME

INDX_FIELD          

INFO_LINE           

INIT_SAL            

INIT_SEX            

INIT_TYPE           

INTERBAG            

JOB_DONE            

JOB_RNG             

JUST_SORT           

KEY_TYPE            

LABNAME             

LAB_UP              

LASTPOPUP           

LAST_DISP           

LAST_INFO           

LAST_LINE           

LAST_POS            

LAST_RECS           

LCBCON              

LEAVE_NOW           

LESS_DEDUC          

LFUZZY              

LINE_CODE           

LINE_NAME           

LINKLINE            

LOW_IND             

LOW_KEY             

LOW_REPORT          

LOW_SCORE

NUM_RECS            

NUM_REPORT

OCR_DISC            

OLDFILE             

OLDPATH             

OP_FILE             

OP_IND              

OUTPUTLINE          

OUT_PCODE           

OVER_LIMIT          

PARM_LINE           

PC_SCORE            

PF_EXTEN            

POSN                

PREFIX              

PRESURNAM2

PRESURNAME

PREVSOUNDS          

PREVWORDS           

PREV_FLAT           

PREV_INDEX          

PREV_KEY            

PREV_NAME           

PREV_PREM           

PREV_SIZE           

PRIMARY_DB          

PROS_RUN            

QUERY_NAME

QUIT_STR            

QUIT_VAL            

QU_DEL_INC          

READ_ONLY           

REC_LENGTH  

REF1

REF2        

REF FILE USE          

REF_FILE

REP NAME             

REPORT_ID           

REPORT_RUN          

REPT_REC            

REP_DEST            

REP_FORMAT

YY               

DB_NOW              

DB_RECNO            

DB_SAVE             

DEACT_WIND          

DEMO_IND            

DEMO_PLACE          

DEMO_VER            

DIR_RES             

DOMAILSORT          

DPS_COUNT           

DROPDEAD  

DUMMY          

EADDL_INFO          

ECURSOR             

EERROR_NUM

ELINE_CODE          

ELINE_NUM           

EMESSAGE            

EPROG_NAME

EQ_COUNTRY          

ERRMSG              

ERROR_CHAR          

EXACTMATCH

FEES                

FIELD_LIST          

FILENAME            

FIRST_TIME          

FLDS_INPUT          

FOR_COUNT         

L_CSTOP             

MAC_RNG             

MAIL_FMT            

MAIN_OPT            

MATCHON             

MATCH_INDX

MATCH_OPT           

MAX_BGWT            

MAX_BUNDLE

MAX_REF             

MEM_FILE            

MENU_SHORT

MERGE_FMT           

MERGE_OPT           

MIN_SELN            

MIXED_WT            

MIX_IND             

MSG_TXT2            

MSS_END             

MSS_START           

MS_DEST             

MS_DESTN            

MS_OUTPUT           

MS_REF              

MS_REPNAME

MS_SERVICE          

MS_SUBCAT           

MS_VERSION          

MULTINAME2

NEW_AN              

NEW_FILE            

NEW_MAT             

NEW_NAME            

NEXTAPP             

NEXT_JOB            

NP_LIB              

NUM_CHECKS

NUM_DUPS            

NUM_FIELDS          

NUM_LETTS           

NUM_LINKS           

NUM_PARMS           

NUM_READ

REP_TYPE            

RES

RETRY_CT            

REX_IND             

REX_START           

RPI                 

RPK                 

RUN_DATE            

RUN_NUMBER

SALN2USE            

SALUTN_IND          

SECOND_DB           

SERIAL_NO           

SETUP_OPT           

SORTON              

SORT_NAMES          

SORT_SCORE

SOUNDARRAY

SPLE_SIZE           

START_DIR           

START_OP            

START_RES           

SURE_TOTAL          

TALKSET             

TBRDESKTOP          

TEXT_IND            

TOP_LIM             

TOTALMATCH

TOTALSCORE          

TOUR_MENUS

TRAN_FROM           

UK_ADDRESS          

USE_UNIQUE          

VERI_POS

VERSION

WALKSORTON

WIN_LAST

WORDARRAY

WPI

WT_ITEM

Y1            

YEAR

YESNO

ZZ

 

  

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