Manually define Historical and RealTime field pairing

If the BatchSchedule table has a field that you need to write to a field in the schTicket table, but the field names need to be different, follow the procedure below to associate the name of the RealTime and Historical fields.

To create a BatchSchedule to schTicket override

1. Create a new configuration JSON file in the following directory:

   %DNADataRoot%\RealTime\config\settings

2. Create a complex object with the following tree structure:

   LMS > BatchXfer > HistoricalTicketFieldOverrides

3. Create a set of keys and values for the field name override. The key should correspond to the name of the Historical field, and the value should correspond to the name of the RealTime field.

   Note: The field names are case-sensitive.

Example: