Account Aggregation not working for Web Service connector

Hi all,

I am trying to onboard a Web service App. The Test connection is successful but I am facing issue when setting up the Account aggregation.

  1. The preview showed data once but isnt showing anything since then
  2. The response mapping is done and I am also getting response on PostMan

What am I missing?

Thanks in advance.

What error are you getting in logs while doing aggregation ?

@msingh900 I can see one attribute “name“ through the preview but can not see the other attribute which are ID(integer), type(String)

If you’re getting ID and type in the response through Postman, most likely the issue is response mapping.

Could you please provide the response structure of the endpoint and information on how have you configured the response mapping in SailPoint?

Please check the configuration and response mapping and other parameters.

Thanks

@zeel_sinojia Below is the response from the API

[

    {

        "id": 1,

        "name": "The Russian",

        "type": "fiction",

        "available": true

    },

    {

        "id": 3,

        "name": "The Vanishing Half",

        "type": "fiction",

        "available": true

    },

    {

        "id": 4,

        "name": "The Midnight Library",

        "type": "fiction",

        "available": true

    },

   

]

Could you also share the snapshot of response mapping?

@zeel_sinojia

Hmm, find it weird that you can see name but not the id and type.

  1. Could you add type attribute here in the response mapping and account schema?
  2. Are there any AfterOperation or Customization Rules configured for this app?

Hi @rishavghoshacc ,

Try updating the schema attribute type as int for the ID attribute

@zeel_sinojia I have already tried that before in place of “id”. It seems that as soon as I add “id“ or “type“ in the mapping and the schema, the preview does not show anything

@uday_kilambi Tried that. It seems that as soon as I add “id“ or “type“ in the mapping and the schema, the preview does not show anything

@rishavghoshacc
Just an quick fix to try on changing the attribute
→ Use user_id instead of id
→ Use user_type instead of type
Then set user_id as integer in the Account Schema (and make it the Identity Attribute if needed).
Update the Response Mapping accordingly, save, and test the preview again.

@sagr0812 @zeel_sinojia @msingh900 @uday_kilambi I suddenly see this is working today. I haven’t mad any changes to the configuration at all

Any reason why this might be happening?

1 Like

@rishavghoshacc Good to know! Might have just been a transient connector or caching issue.