NativeIdentity update after create account

[Manju22 (Manjuladevi Manickam)]

Hi Team,

We are observing that the NativeIdentity is not getting updated immediately after account creation in the WebService Connector. It appears to be updated only after the subsequent aggregation.

Could you please confirm if this is the expected behavior?

Additionally, is there a way to update the NativeIdentity immediately after account creation or during the creation?

At present, since the NativeIdentity is showing as “???”, multiple access provisioning is not being triggered.

I need to map UserId as NativeIdentity which is application generated number which I will get in Create account response body only.

{

    "data": {

        "userId": 532

    },

    "error": {},

    "links": {}

}

Kindly advise on how this can be addressed.

Thanks,

Manju

[suraj_gorle]

@Manju22

Thanks,

Manju

Hi @Manju22 ,

Can you please map nativeIdentity in response mapping of create account operation. Also check the account activity and share here screenshot by masking sensitive info.

[BhanuK1 (Bhanu Kondi)]

Hi @Manju22 ,
In the create account response mapping, make sure you have correctly mapped userId to the nativeIdentity attribute.
Additionally, you can also configure Get object to aggregate the single account, which will be called right after create account operation

[mshivraj10 (Manish Shivraj)]

Hi @Manju22 ,

There could be two possibilities:

1. check get object operation that you have mapped response properly. The response should be same as Account Aggregation.
2. check if Identity attribute returned from get Single user API endpoint.

[Manju22 (Manjuladevi Manickam)]

Response mapping in the create account helped to update native identity after the account creation. Thanks.