Org Web Adapter

Editing pages/eng_13593_proceed_with_import_in_case_of_row_based_errors_in_workday.org

:PROPERTIES:
:ID:       bf892886-71b8-44ac-8f61-2165bc9a1564
:ROAM_ALIASES: ENG-13593
:END:
#+title: ENG-13593 - Proceed with import in case of row based errors in Workday

- tags :: [[id:b71b60df-d439-4aa1-8c2c-265707adf8ec][Jira]] [[id:b08ac197-337b-4392-84d5-98eaead61400][15Five]] [[id:48ec7ad9-9d6e-47ec-878e-6d1dce1a830a][Workday Integration with 15Five]] [[id:077e9eee-3cb9-4110-8be1-44ef4f698600][Bugs]]

* Description
/This is a time-boxed ticket./

As a company admin, I expect my Workday import to not be interrupted by row-based errors

AC:
1. The system should proceed with data import in case row-based errors were identified (even in case of only one valid row).

2. Errored rows should neither affect an existing profile nor create a new profile.

3. Errored rows should be stored in ff_bulkimporthistory together with valid rows.
4. Errored rows which were not imported should be discluded from People imported stats

5. Would be ideal if the solution here is Workday-specific and does not affect the logic of other provisioning options
6. Import status is "Successfully imported" if at least one profile was successfully imported, e.g. the system failed to import 99 out of 100 profiles because of errors.

If we feel like #5 is not possible, please outline what will need to be done globally and how it will impact our other provisioning options. And then Harry can run that by the SMEs in Success and Support.