ConnectALL automation with flat file adapter stopped working after adding more fields

Products

• ConnectAll SaaS
• ConnectALL
• ConnectAll On-Prem

Issue/Introduction

We are trying to get our Flat File Automation working.  We were able to successfully import a small subset of fields, but when we mapped additional fields and pointed to a new csv file we are not seeing anything in the log files.  We do see the job lock and have set the rerun parameters but nothing is showing up in Rally and there is nothing in the log file for the runs.  We did get one error about the Id file which we corrected and nothing is showing in the log file since.

 

Steps to Reproduce:

1. Configure a ConnectALL Flat File Automation with a small subset of fields.
2. Successfully import data from a CSV file to Rally.
3. Map additional fields in the automation configuration.
4. Point the automation to a new CSV file containing the additional fields.
5. Run the automation and monitor the log files for activity.

 

Actual Results

The job appears to lock as if running, but no data is synchronized to Rally.
Log files show no new entries for several minutes, or eventually report: java.lang.IllegalArgumentException: Mapping for Id not found, expected one of [..., Id].
The "Id" field appears to be present in the file but is not recognized by the adapter.

 

Expected Results

The automation should parse the new CSV file, map all fields correctly, and synchronize the records to Rally with corresponding log entries.

 

Environment

4.1.0

Cause

The CSV file was saved with UTF-8 BOM (Byte Order Mark) encoding. The BOM is an invisible special character added to the beginning of the file, which ConnectALL interpreted as part of the first column header (making it Id instead of Id). This prevented the adapter from matching the header to the configured field mapping.

Caused by: java.lang.IllegalArgumentException: Mapping for Id not found, expected one of [acmxnumberm2f, Area, bax5b, Category, Closed By, Closed Date, closexreasonc0e, Computer, Creation Date, Current Estimate (hrs), deploymentxinstructionst2d, Description, developerl3c, Due Date, Elapsed (hrs), Milestone, Name, Notes, Opened By, Original Estimate (hrs), Owner, Parent Case ID, Priority, Project, qacxtestingc110, Release Notes, Resolved By, Resolved Date, rixstateG34, Root Case ID, smei6a, State, Status, Story Points, Ticket, Version, �Id]

Resolution

The file encoding was changed from UTF-8 with BOM to standard UTF-8. Once the invisible character was removed and the file was re-uploaded, the Flat File adapter correctly identified the "Id" field and synchronization resumed successfully.