Webservice get account

[DivyaL_7 (Divya L)]

Hi everyone, I’m new to SailPoint and currently working with a Web Services connector. I’m running into an issue where the NativeIdentity field for accounts is not being populated correctly — instead, it just shows ????.

Here’s my setup:

• My NativeIdentity is defined as USER_ID.

• When I create an account using the endpoint:

  POST api_url/v1/users
  
  

  The API returns a response body like this:

  {
    "link_user": "api_url/v1/users/USER_ID"
  }
  
  

  → The USER_ID is correctly created in the target system.

• However, when I configure the Get Account call, I use this URL:

  GET api_url/v1/users/$plan.getNativeIdentity$
  
  

The problem is that the Create Account response does not directly return the USER_ID (only the full link), so SailPoint doesn’t seem to know how to populate the NativeIdentity value on the account.

Question:
Has anyone faced this situation before? How can I get SailPoint to extract the USER_ID from the create account response so that the NativeIdentity gets filled properly?

[nsammut (Nick Sammut)]

For the Get Object operation, you have to use $getobject.nativeIdentity$ instead. But because the Create endpoint doesn’t return the user id for it to be used in the Get Object, likely a Web Service After Operation Rule might need to be used to change the json response to only include the user id. There may be other fancy ways to use an operation with a parent endpoint with the use of the $response variable… but I’m not sure it’d work in this case.

Get Object

Web Services After Operation Rule

[JackSparrow (Theja C)]

Hi @DivyaL_7 ,

Have you configured response mapping correctly in CREATE ACCOUNT operation?

Check this post The target source's nativeIdentity is missing during the create operation using the WSC