The user record is being updated by the SF User Connector even though their TERMINATION DATE is before HIREDATE in BizX (and in the input file). When this condition is met, an exception error should be triggered and the user record concerned should not be updated. In addition, this exception error should be detailed in the corresponding connector job report.
Learning Management System (LMS)
Reproducing the Issue
- In BizX: In a user's profile make sure TERMINATION DATE is before HIREDATE
- In LMS: Run the SF User Connector
- User record where this condition is met updates successfully without Exception Error Message in Connector Report
This is a legacy issue where the exception error is not triggered by the connector when HIREDATE & TERMINATION DATE are in two separate files (in the same connector job). For example, HIREDATE might be exported by BizX in the user_data file and the Termination Date might be exported in the extended_user_data file.
Whilst this will be fixed in 1608, and the exception will be flagged even if these fields are exported to different files, the workaround is to make sure these two fields are exported to the same data file (Eg. user_data file). To achieve this the export feed from BizX needs to be reconfigured and mapped accordingly in the LMS.
* Issue already fixed in 1605 patch. Validation checks performed across both files so if TERM_DTE is earlier than HIREDATE in either file, this will trigger the exception and the record will not be updated.
LMS; SF User Connector; HIREDATE; Termination Date , KBA , LOD-SF-LMS-CON , Connectors , Problem