Account getting suspended on UpdateAccountTask

[Anu]

We have an salesforce application where provisioning via REST connector and Recon via salesforce connector is setup.
We are seeing a strange behavior, When an user update rule triggers "update account task", upon task completion user's account status is changing to deleted status(suspended from import service).

However account in target is still active, Even the next reconciliation is not updating status/bringing account. No orphans are created and reconciliation rules is as follows which will match as per the data.

User Correlation Rule with values::

Rule1: User email(xxx@ddd.com): accounts cp4(xxx@ddd.com)

[AmitM]

Hi @Anu , can you share the update account json.

Also, I hope you are using the same service principle for rest connector and ootb.

Thanks,

Amit

[Anu]

@AmitM Thanks for the response. PFA updateaccountJSON for reference

[rushikeshvartak]

• Check Status threshold config of Salesforce application 
• confirm if status changes after import ?

[Anu]

@rushikeshvartak  Thanks for the response .Below is the status threshold config and yes the status changes after import

{
"statusAndThresholdConfig": {
"accountThresholdValue": 1000,
"statusColumn": "customproperty10",
"activeStatus": [
"true"
],
"deleteLinks": true,
"inactivateAccountsNotInFile": false,
"correlateInactiveAccounts": true,
"lockedStatusColumn": "customproperty22",
"lockedStatusMapping": {
"Locked": [
"1"
],
"Unlocked": [
"0"
]
}
}
}

[rushikeshvartak]

What is value of cp10 for account

[Anu]

@rushikeshvartak The cp10 value is true which means the user is still active in target

[AmitM]

Hi Anu, there is nothing in update account JSON that could result in the challenge you are facing.

It has to  be either Status mapping. Or as I said in my original post a permission issue where the user that you are modifying with changes Salesforce object in a way that your recon service principle can't fetch it. If you are using same SP then most probably status. Try to use what I have shared below.

"status": "IsActive~#~bool",

We are mapping status directly and it works for us. 

{
"accountfield_mapping": {
"accountID":"Id~#~char",
"name":"Username~#~char",
"accounttype":"UserType~#~char",
"updateUser":"LastModifiedById~#~char",
"updatedate":"SystemModstamp~#~date",
"lastlogondate":"LastLoginDate~#~date",
"lastpasswordchange":"LastPasswordChangeDate~#~date",
"CREATED_ON":"CreatedDate~#~date",
"creator":"CreatedById~#~char",
"displayName":"Name~#~char",
"status": "IsActive~#~bool",
"customproperty1":"FirstName~#~char",
"customproperty2":"LastName~#~char",
"customproperty3":"CompanyName~#~char",
"customproperty4":"Email~#~char",
"customproperty5":"UserRoleId~#~char",
"customproperty6":"ProfileId~#~char",
"customproperty7":"ManagerId~#~char",
"customproperty8":"LastModifiedDate~#~date",
"customproperty11":"Country~#~char",
"customproperty12":"Title~#~char",
"customproperty13":"FederationIdentifier~#~char",
"customproperty14":"Department~#~char",
"customproperty15":"Liner_Brand__c~#~char",
"customproperty16":"Cluster__c~#~char",
"customproperty17":"CM_Visibility__c~#~char",
"customproperty18":"Region__c~#~char",
"customproperty20":"UserPermissionsSupportUser~#~bool",
"customproperty21":"Reason_For_Deactivation__c~#~char"
}
}

Thanks,

Amit