Duplicate entry for Inactive Account - Rest Connector

[Sivagami]

Hi Team

When we are performing account import for any application using REST connector with status config (defining which accounts to be marked as active and which accounts needs to be marked as inactive), we are having issue with account status. If the account is active it's reflecting as expected but if an account is inactive it's creating the same account again with inactive status. So in each import, if an account is inactive, the number of accounts is increasing. Please provide some insight.

"statusAndThresholdConfig": {
"statusColumn": "customproperty11",
"activeStatus": [
"active"
],
"deleteLinks": true,
"accountThresholdValue": 1000,
"correlateInactiveAccounts": false,
"inactivateAccountsNotInFile": true,
"deleteAccEntForActiveAccounts": true
}

This issue was posted in the legacy community forum but not answered - https://forums.saviynt.com/t5/general-discussions/duplicate-entry-for-inactive-account-rest-connecto... . Posting it again to get some traction.

Note: Have noted this issue only in 5.5 SP 3.x and 5.5 SP 5.x. This issue does not occur in 2020.x, 2021.x, 2022.x with the exact same connector jsons which rules out the root cause to be json issue.

Does anyone5.5 SP 3.x / 5.5 SP 5.x versions come across the same issue? If so, what was done to resolve the problem?

Any insights in this regard are much appreciated.

-Siva

[sagars]

Hello @Sivagami ,

The Status threshold looks good, This might be an issue if the accountid and account name is not  unique at target or the saviynt DB level. 

What are you seeing in the logs? Usually this config will kick in at the end of the job. Please check and share details.

Regards,
Sagar Srikantaiah

[Sivagami]

Thanks Sagar for the response. I have shared the logs with you for reference. 

[sagars]

Hello @Sivagami ,

Do you see any account status as null? Can you check if you correct account status from initial run?

select distinct status from accounts where endpointkey = X;

Regards,
Sagar Srikantaiah

[Sivagami]

Hi Sagar,

There are no accounts with status as null.

[rushikeshvartak]

1. Did you changed accountId mapping in colsToPropMaps ?
2. can you try adding inactive status in statusConfig

[Sivagami]

1. Did you changed accountId mapping in colsToPropMaps ? - From connector go live, we have not changed the account id mapping. 
2. can you try adding inactive status in statusConfig - Tried adding something like below as well, no luck. 

"statusConfig": {
          "active": "true",
          "inactive": "false"
}

I just picked a sample connector that users this status config and tried using the exact same jsons. Still it creates duplicate inactive account for us. Again, this happens only in 5.5 SP 3.x version and not in v2021. Exact same json that we use currently, doesn't create duplicates in v2021

https://saviynt.freshdesk.com/support/solutions/articles/43000568985-slack-connector-guide 

[rushikeshvartak]

can you check on constraints applied on accounts table in DB

[Belwyn]

Hi @Sivagami 

Where you able to check what Sagars has suggested? 

Thanks & Regards, 

Belwyn.

[Sivagami]

Yes, I just did.