Transform v3 differences from older API

Identity Security Cloud (ISC) ISC Discussion and Questions
1

We have an existing transform that can be pulled using the GET method with {{api-url}}/v3/transforms as well as {{url}}/api/transform/list

The issue is that we made an update using v3 and this is not reflected using the older API. So the other team member did not see the updates I made.

I noticed the id is different between the two:

older: name
newer: generated

There is also a name field on the v3 list. I understand we can move towards the newer API but just trying to figure out how these are identified on the back end since in the mapping it shows only one which happens to be the newer version.

2

Hi @ethompson,

All the Transforms are available in V3 API (transform created using V3 API & V1 API). In backend V3 API is called which gets all the available transforms.

Regards,
Anamica

3

Hello @ethompson,

I did confirm that updates made with v3 are not reflected in the v1 API. I am going to take this back to our engineering team.

To give a little more info on the Ids:

The below example is a lookup transform taken from the GET https://{{tenant}}.api.identitynow.com/cc/api/transform/list v1 API.

{
            "id": "CityToRegion",
            "type": "lookup"
            "attributes": {
                "table": {
                    "New York": "Americas",
                    "Munich": "Europe",
                    "Brussels": "Europe",
                    "default": "",
                    "Singapore": "Asia-Pacific",
                    "Tokyo": "Asia-Pacific",
                    "Taipei": "Asia-Pacific",
                    "London": "Europe",
                    "Austin": "Americas",
                    "Sao Paulo": "Americas",
                    "San Jose": "Americas",
                    "Boston": "Americas"
                }
            }
        }

The same transform pulled with the v3 API https://{{tenant}}.api.identitynow.com/v3/transforms

{
        "id": "9511367b-3d78-4331-abbf-800342fbd3fc",
        "name": "CityToRegion",
        "type": "lookup",
        "attributes": {
            "table": {
                "New York": "Americas",
                "Munich": "Europe",
                "Brussels": "Europe",
                "default": "",
                "Singapore": "Asia-Pacific",
                "Tokyo": "Asia-Pacific",
                "Taipei": "Asia-Pacific",
                "London": "Europe",
                "Austin": "Americas",
                "Sao Paulo": "Americas",
                "San Jose": "Americas",
                "Boston": "Americas",
                "Test": "Test-Region"
            }
        },
        "internal": false
    }

In the v3 transforms you are correct in that the id is autogenerated and is used in other API calls to uniquely refer to the transform. In the v1 API the name property was the unique property used to refer to the transform and used to update and delete via the API. The name property is still on the transform in v3 but now the autogenerated id is used to uniquely identify the transform when calling the API.

1 Like