Uploaded image for project: 'CFA MX '
  1. CFA MX
  2. CFAMX-16560

Identity File processing -Skip records with non-integer personid/log error message and continue file processing

    Details

    • Type: Testing Defect
    • Status: Done (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Sprint:
      2021.R6 CloudLink Sprint 6

      Description

      Scenario - TeamMember All file is loaded that contains 4 records. Record #1 and #3  have matching personid = 2391855. Record #2 has a personid with a non -integer value (256t045). Record #4 is good (no issues). See attached file.

      When loaded and the Team Member Incremental Identity Import is processed in testing

      Record #1 is processed 

      Record #2 logs a format issue (See log below)

      Records #3 and #4 are both skipped

       

       

      Currently Log displays :   Event : 9/13/2021 6:26:47 PM : Employees Data Import on 9/13/2021 6:26:47 PM : Starting Data Import
      Event : 9/13/2021 6:26:47 PM : Data Import on 9/13/2021 6:26:47 PM : Source File \\ATL2CFANPV002\CFATesting\DataImports\Identities\20210620_Contractor_all_duplicatandNonInteger.xml successfully validated
      Event : 9/13/2021 6:26:47 PM : Data Import on 9/13/2021 6:26:47 PM : Record #1 parsed
      Event : 9/13/2021 6:26:47 PM : Employee Data Import on 9/13/2021 6:26:47 PM : Record #1 : Updated employee records for Employee 00021855360a487b82ade74e31da8d2d - Brian Gronberg

      Error : 9/13/2021 6:26:47 PM : Employees Data Import on 9/13/2021 6:26:47 PM : Task threw exception System.FormatException: Input string was not in a correct format.
      at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
      at System.Number.ParseInt64(String value, NumberStyles options, NumberFormatInfo numfmt)
      at System.String.System.IConvertible.ToInt64(IFormatProvider provider)
      at System.Convert.ChangeType(Object value, Type conversionType, IFormatProvider provider)
      at Mx.Common.Data.DataHelper.TryGetValueFromDictionary[T](IDictionary dictionary, String key, T defaultValue)
      at Mx.BusinessObjects.EmployeeImport..ctor(IDictionary dictionary)
      at Mx.Services.EmployeeImportMapProvider.CreateRecord(IDictionary dictionary)
      at Mx.Services.XmlImportSourceProvider.MoveNext()
      at Mx.Services.ImportService.Import(DataImportClassSet importClassSet, IImportSourceProvider importSource, ImportLoggingLevel logLevel, ITaskController taskController, DataImportTask dataImportTask, BusinessUser executingUser, List`1 newSourceFilePaths, List`1 importLog)
      Event : 9/13/2021 6:26:47 PM : Employees Data Import on 9/13/2021 6:26:47 PM : Data Import Complete

       

      Defect

      The requirement for skipping and continuing processing is not occurring. When an exception is thrown the process completely fails and no further processing is done. In this case - as you can see by the log above. Records #3 and #4 are never processed. 

      NOTE: In the case of record #3 this will be skipped since it contains a duplicate Person ID - this should be skipped and a message should be logged. This seems to work when personid for all records are integers prior to the failure.

       

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                charles.wheeler Charles Wheeler
                Reporter:
                charles.wheeler Charles Wheeler
              • Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  PagerDuty

                  Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.