Legacy Context File Configuration (GBUCS Architecture)

For RI interfaces in environments created from version 19 and earlier (including environments currently on v21 that were provisioned with v19), a more basic CTX context file is used. These context files only accept a list of columns in the data file; they cannot control any formatting or other options. They also must have a fixed filename ending in .dat.ctx regardless of the associated file. Use the name of the target table in RI as the file name. For example, CALENDAR.csv will have a context file named W_MCAL_PERIOD_DTS.dat.ctx. The file format itself is also fixed. CSV files will be comma-delimited, while DAT files will be pipe-delimited. DAT files use the same name for both the data file and context file, such as W_CODE_DS.dat and W_CODE_DS.dat.ctx.

For a complete list of mappings between CSV filenames and associated table names used for CTX file naming, refer to Context File Table Reference .

The following is an example context file for the CALENDAR.csv data file:

File Name: W_MCAL_PERIOD_DTS.dat.ctx

File Contents:

MCAL_CAL_ID
MCAL_PERIOD_TYPE
MCAL_PERIOD_NAME
MCAL_PERIOD
MCAL_PERIOD_ST_DT
MCAL_PERIOD_END_DT
MCAL_QTR
MCAL_YEAR
MCAL_QTR_START_DT
MCAL_QTR_END_DT
MCAL_YEAR_START_DT
MCAL_YEAR_END_DT

Note:

This legacy context file format applies strictly to Retail Insights. Science applications do not support the legacy context file format; they expect the full data file contents in their interfaces.