Web Services SaaS - Use of JSONPath in Account Aggregation

[acosson (Adrien Cosson)]

Hi folks !
I have the below JSON response from a Webservice connector as authoritative source to import identities for our customer, where all objects are contained in “workers” list.

{
    "workers": [
        {
            "workAssignments": [
                {
                    "customFieldGroup": {
                        "stringFields": [
                            {
                                "itemID": "PTP",
                                "stringValue": "Responsable"
                            },
                            {
                                "itemID": "SAD_LIB34",
                                "stringValue": "SIEGE"
                            }
                        ]
                    }
                }
            ]
        }
    ]
}

I need to get the value “SIEGE” in stringValue key and tried the below, which is valid on https://jsonpath.com/, but seems not to be working in ISC.

workAssignments[0].customFieldGroup.stringFields[?(@.itemID == 'SAD_LIB34')].stringValue

Any help is much appreciated !

[j_place (Jeremy Place)]

Hi Adrien. Welcome to the community!

You are coming across the “filter returns an array” scenario. If you use the SailPoint jsonpath evaluator at SailPoint Developer Community you will see how ISC parses it.

Can you make the attribute multi-valued?

More info at JSONPath - filtered query returns array rather than string

[acosson (Adrien Cosson)]

Good day Jeremy !
I have tried the below using the JSONPath evaluator for ISC, and it effectively returns an array as you mentioned :

I did update the Mapping information as following :

workAssignments[0].customFieldGroup.stringFields[?(@.itemID == 'SAD_LIB34')].stringValue

into the “sector” attribute, and made the same attribute in account schema as Multi-Valued :

However it seems reconciliation does not bring the value into the account attribute :

Anything else should we consider ?

[acosson (Adrien Cosson)]

Following investigations, I have identified this is working in a WebService connector that goes through Virtual Appliances, but is not supported on the SaaS connector.