2343608 - Multiple input files not working in Learning History Connector

Customer have enabled the multiple file processing in System Configuration and renamed the txt input files to indicate that there are multiple versions, but the system does not process these multiple input files fine.

In one scenario the system says that the files have been processed but no entry is found in the actual learning history.   In that scenario Customer have saved tie file as any file type (so it actually doesnt look like a real txt file anymore). So that might be the problem, but this was the only way to prevent that the file name carries the indication ".txt" twice (see scenario below).

In the other scenario the system says that the input file cannot be found. In that scenario Customer have saved the file as txt file (learninghistory_data_worldfood.txt.1) but as soon as I put it on the server the file name is automatically changed to this strange construction by adding "txt" again at the very end of the file (learninghistory_data_worldfood.txt.1.txt).

 

• Learning Management System

Multiple Input File Processing

The connectors can process multiple input files.  The user connector files are by default multiple file enabled.  Each connector has a property that enables multiple file processing.  It is the connector.input.file.multiple property.  Add this property to the specific connector.  For example:

Enabling the Item Connector:  item.connector.input.file.multiple=true

Enabling the Learning History Connector:  learninghistory.connector.input.file.multiple=true

Once enabled, the input files will have a numeric suffix.  For example, if you had two files to process in a single run then you would name the two separate files as:  item_data.txt.1 and item_data.txt.2.  The numeric suffix cannot have leading zeroes.  They must be 1, 2, 3 – NOT 01, 02, 03.

• Multiple input files connectors
• Learning history multiple input files
• connectors issue

, KBA , LOD-SF-LMS , Learning Management System , LOD-SF-LMS-CON , Connectors , Problem

SAP SuccessFactors HCM Core 1602