Encountering Issue with Advanced Queries: Removal of Leading Zeros in Integer Values

[KTaggart]

When creating a technical rule in Saviynt using Advance Query, we are encountering an issue related to how integer values are handled, particularly those starting with zero, such as department numbers, job codes (e.g., 002000, 002010) etc. Presently, when comparing these values with Saviynt, they are not considered identical because the leading zeros are being removed during the data comparison process.

Please follow below steps to Reproduce this issue.

1. Navigate to Admin > Identity Repository > Technical rules.

2. Select Create Technical Rule.

3. Enter a Rule Name and Rule Description.

4. Apply the following condition in advance Query,

DepartmentNumber = 0115

5. Click on Preview to view the list of users satisfying the condition.

6. Users with a Department Number that is "0115" are not included in the list, while those with a Department Number that is "115" are included in the list.

[DaanishJawed]

Hi @KTaggart ,

Please try with the below in the advance query -

a.departmentNumber = 0115

Thanks.

[KTaggart]

Hello,

I am getting an equal number of results in both scenarios.

Users with a Department Number that is "0115" are not included in the list, while those with a Department Number that is "115" are included in the list in both the scenarios

Advance Query 1 - DepartmentNumber=0115

Total users - 804

Advance Query 2 - a.departmentNumber = 0115

Total users - 804

[timchengappa]

Hi @KTaggart 

Please try using the department number in quotes...

E.g. departNumber = ‘0115’

[Manu269]

@timchengappa is this a bug?

Can you also help us to share the attributes in case the values are managed in job code and any custom property attributes?

[KTaggart]

Yes, that is the workaround we are using currently.

[rushikeshvartak · Accepted solution]

SELECT TRIM(LEADING '0' FROM employeeid) AS stripped_number
FROM users;