# Version 9.1.141 (3 February 2025)

#### **Imports**

##### Employee data import error (#125558)

**Problem**

- The org nodes are duplicated when no org structure exists and multiple users are linked to the node
- When importing nodes with accents in the name the import fails
- The bulk import to V8 for the job structure is blocked by the full org structure import when errors occur

**Solution**

- Remove unused caching check between node creation and replace with existence check on the newly created nodes
- Add accent escapes when querying the existing org nodes.
- Reorder the bulk import types

##### User Import: Change appointment import to import by action type (#121473)

**Problem**

<div id="bkmrk-when-a-user-is-termi">- When a user is terminated or transferred in the same file the user conflicts with a new user taking the same position

</div><div id="bkmrk-the-old-user-was-ter">- - The old User was terminated and the New user was appointed in the same position within the same import after the termination
    - The old user transfers to a new position and the new user receives the old user's position after the transfer

<div>- When the position is changed but the start date of the appointment remains the same the user appointment is not corrected

</div></div><div id="bkmrk-"></div><div id="bkmrk--1"></div><div id="bkmrk-appointment-import-r"><div>**Appointment Import Rules**</div><div> </div><div>**Terminations**</div>- When an end date is provided for the active position 
    - With a termination reason, end on the imported date with the reason provided
    - Without a termination reason, end the active appointment with the date 
        - Clear the current termination reasons if they exist
- When the terminated record imported's position is different from the latest appointment position the system handles the record as a transfer to a terminated position
- When the terminated record imported is on the same position but the start date, termination date, appointment type, and termination reason differ handle it as an appointment correction
- When no appointment exists and the user is imported with an end date handle as a new appointment

<div>**New Appointments** </div><div>- When a user has no appointments in the system

</div>- - Check for overlapping appointments for the position 
        - The start and end date of the imported position must not overlap any existing appointment for the position
    - The appointment type must exist as master data

<div>**Transfers**</div><div> </div>- When the user has current appointments in the system, terminated or active
- The user's latest appointment is active

<div>- - Check for overlapping appointments for the position

</div><div>- - - The start and end date of the imported position must not overlap any existing appointment for the position
    - Check for overlapping appointments with the current user's appointments and other than active
    - The appointment type must exist as master data
    - End the current active appointment with end date = new appointment start date -1

<div>- The user's latest appointment is terminated

</div><div>- - Check for overlapping appointments for the position 
        - The start and end date of the imported position must not overlap any existing appointment for the position
    - Check for overlapping appointments with the current user's appointments
    - The appointment type must exist as master data

</div></div><div> </div><div>**Appointment Corrections**</div>- The user has an appointment 
    - The latest appointment position matches the import position appointment
    - The start date, end date, appointment type, and termination reason differ from the latest appointment for the user
    - Check for overlapping appointments for the position 
        - The start and end date of the imported position must not overlap any existing appointment for the position
    - Check for overlapping appointments with the current user's appointments
    - The appointment type must exist as master data

</div>---

#### **Report Builder**

##### Auto-scroll when dragging and dropping columns (#123392)

**Problem**

- When dragging and dropping a column to another position, you can only drag to the field that is left on the screen, even if there are other fields to the left of the list.
- This means that you must drop the field where you can, wait for the page to reload, scroll to the field again and drag it further left.

**Solution**

- While dragging it “past the left”, the result set must scroll to the right until you get to the preferred fields and then drop the column

---