Project

General

Profile

Production Ticket(ST) #11384

Customer Data Import Issues

Added by Rashdan Hussin 6 months ago. Updated 4 months ago.

Status:
Ticket Resolved
Priority:
P3 - Medium
Assignee:
Start date:
05/04/2024
Due date:
17/05/2024
% Done:

0%

Estimated time:
Job Remark:
Ticket Logged Date:
05/04/2024
Ticket No.:
Related Ticket ID:
Type:
Support Request
SLA Initial Response:
06/04/2024
SLA Delivery:
19/04/2024
Esclation Time:
Issue Reoccurance#:
Actual Initial Response:
Resolution:

L3 CU: https://app.clickup.com/t/86epb6dnk

Requester ExpectedDeliveryDate:
Delay Justification:
Priority Seq:
Effort (Hour):
External Ticket #:

None


Description

The issue happen in two cases:

1. Case 1: Incomplete Data Entry
- We've identified instances where all data imported via the web interface is not entering our database.

2. Case 2: Partial Data Entry
- Additionally, there are occurrences where only a portion of the new data is being entered into the database.

Upon investigation, we have determined that these issues stem from two main factors:
- Excessive loading times during the import process
- Issues with customer data relations

History

#1 Updated by Muhammad Arif 5 months ago

  • Due date changed from 19/04/2024 to 30/04/2024

#2 Updated by Muhammad Arif 4 months ago

  • Due date changed from 30/04/2024 to 17/05/2024
  • Status changed from Assigned To to Support In Progress

#3 Updated by Muhammad Arif 4 months ago

  • Status changed from Support In Progress to Escalated to Level 3
  • Resolution updated (diff)

@Mcc Jann as tested, if using xlsx file in route plan module, there is no issue to import but if using csv file will hit oledb error.

in customer import module, xlsx file cant be uploaded due to oledb error.

in this case, can we apply same logic for xlsx file for customer module?

L3 CU: https://app.clickup.com/t/86epb6dnk

#4 Updated by Muhammad Arif 4 months ago

  • Status changed from Escalated to Level 3 to Ticket Resolved

Also available in: Atom PDF