Handling of .cfg Files in Text File Data Reader
In Board 12 & 14, the Text File Data Reader has a limitation in how it handles .cfg files when a pattern filter is used in the "Connection" tab. This impacts the automatic mapping of fields and the correct configuration of the file settings, such as delimiters, headers, and other parameters stored in the .cfg file.
Issue Overview
When a pattern filter is set to "Sales.*", Board successfully connects to the "Sales.csv" file and loads the configuration and mapping from the "Sales.cfg" file. However, when the pattern filter is set specifically to "Sales.csv", Board connects to the file but fails to load the associated .cfg information, leading to missing field mappings and incorrect file configurations.
This means that important configuration details—like separators, headers, and field structure—are not applied, even though a valid .cfg file is available. As a result, users have to manually set these parameters, increasing the likelihood of errors and adding unnecessary steps to the data import process.
Proposed Solution
In Board 10, the ASCII Data Readers consistently loaded information from .cfg files, regardless of whether the pattern filter specified file types. We propose restoring this behavior in the latest versions of Board to ensure that .cfg files are always utilized for configuration and mapping, regardless of the pattern filter applied.