Hi Sanjay

When testing the Upload templates created as per Reference Case No: L12552 and found the below issues in "uploading of KPI Maintenance". Refer query below:

When uploading KPI Maintenance, there are facing validation errors: below is a comparison of 2 rows that have both dash characters.

1. Column "D" in the KPI Maintenance excel is "KPIType"
2. Row 4 KPI type is "HCM - Succession Planning development and upskilling" 
3. and Row 11 KPI Type is "IT - Security Enhancement"
4. Both these KPI Type's are already created in the system
5. Both the KPI Type's have a dash (-)
6. However, when uploading, Row 4 says failed but Row 11 is validated

This is being tested in their training environment, requesting if we can take a look into this. 

They have requested to allow commas, full stop, dashes, quotation (, . - ; ), etc when performing the upload process.

Hi Sanjay

Issue replicated – refer environment details:

1. URL: 10.0.0.18/LINKSOFT
2. Database: Link Technologies - DEMO
3. Login: standard Link Admin username and password

Scenario:

1. Uploaded KPI Types using excel “CompanyAdministrationDropdown”
2. This was successfully uploaded
3. Now uploaded KPI Maintenance using excel “PerformanceManagementKPIMaintenance”
4. Received validation error “Failed - KPI Type is Invalid” in lines 4, 9, and 10. Refer to Figure 1.
5. Verified the KPI Type in line 4 “HCM - Succession Planning| development and upskilling” – this was uploaded successfully in step 1. Refer to Figure 2.

Refer to Figure 1:

Refer to Figure 2:

Hi Aarti, I had a look at this and found that the KPI TYPE should not exceed 50 Characters. This is the initial design of the system.

I will release a patch with the validation message stating the issue. We can look at extending the field width in future versions.

I will leave the case assigned to Development so we can issue a Patch for this validation.

Skype Message:

AARTI

Hi Aarti,

1. The change will be available in version: 13.30 and PATCH for V13.20 as 13.20.0203

2. The following changes were made(Include Database object names, Program classes, and any other relevant information):

1. Changed the KPI Maintenance upload file to use CODE instead of Description. The code is limited to 50 characters
2. Added validations for File upload in the areas specified in Table 1

3. Affected Areas:

1. File Upload for Leave Transactions and KPI Maintenance

4. The issue was caused by:

1. Upload template should use Code instead of Description. This will allow users to use large descriptions while maintaining 50 characters in the "Code" fields.

5. Other Relevant Notes: 
6. Next Step (Review and System Test (Developer) -> UAT (Quality) -> Documentation): UAT

PART B - Development Reference (Place descriptor for objects changed):

Table 1 - Added validations for the following codes

Environment Details

1. OS version: Win10
2. Application version: 13.30
3. Setup on:
   1. Server: LinkQA4
   2. Database: LinkSOFT
   3. LinkSOFT URL: HTTP://LinkQA4/LinkSOFT
4. Login Details: Standard username and password for user "admin"

Next Step: UAT on 13.20 and Closure

The following tests were performed:

Table 1 - Test Results

Environment Details

1. Application version: 13
2. URL: 10.0.0.18/LINKSOFT
3. Database: Link Technologies - DEMO
4. Login: standard Link Admin username and password

Hi Sanjay

There is one particular KPI Maintenance that is failing to upload. The codes for KPIType, ScoreType, and ScoreFormat are active in its maintenance tables, however, uploading this KPI gives we get this error message:

"Failed - Data is invalid. Expected 7 columns.KPI Type cannot be more than 50 characters in length ScoreType cannot be more than 1 character in length Score Format is Invalid" 

There are other KPI Maintenances that are using the same "ScoreType, and ScoreFormat" but these have been uploaded successfully.

Refer to Figure 1: KPI Maintenance Upload Validation 

Issue replicated in the demo database– refer to environment details:

1. URL: 10.0.0.18/LINKSOFT
2. Database: Link Technologies - DEMO
3. Login: standard Link Admin username and password

Regards
Aarti

Hi Aarti, your data has a "comma" in the content. When importing CSV you cannot have that. The definition of CSV is Comma Separated Values, which means a "comma" is the data separator.

Remove that and you should be ok.

Hi Sanjay

TLTB has advised that some data contents will have commas and requested alternative ways to achieve this.

What is the best solution we can come up with?

Regards
Aarti

Hi Sanjay

Is there any other import mechanism that can be used?

Regards
Aarti