and more in a single search tool across platforms. Read the announcement here. |
03/27/2024 03:22 AM - last edited on 03/27/2024 06:03 AM by Sunil
Hi Team,
I have two different call for import account from Target. in the 1st call we are importing id, email and in the next call will get all information. How we can achieve this ?
ImportAccountEntJSON :
03/27/2024 01:27 PM
Disclaimer - This is an AI generated response and the feedback on this thread will be used to fine tune.
To achieve sequential and iterative account import with two different calls where the first call imports basic information (id, email) and the second call fetches additional details based on the ids fetched from the first call, you should structure your ImportAccountEntJSON to properly sequence these calls and handle dependencies. Here's an approach to structure your JSON for such a scenario:
{
"accountParams": {
"connection": "accAuth",
"processingType": "SequentialAndIterative",
"call": [
{
"callOrder": 0,
"stageNumber": 0,
"http": {
"url": "https://XXXXX/netsuite-rest/igam",
"httpHeaders": {
"Authorization": "${access_token}",
"Accept": "*/*"
},
"httpContentType": "application/json",
"httpParams": {
"type": "user",
"action": "getlist"
},
"httpMethod": "POST"
},
"listField": "records",
"keyField": "accountID",
"colsToPropsMap": {
"accountID": "id~#~char",
"name": "email~#~char",
"customproperty1": "employee name~#~char"
}
},
{
"callOrder": 1,
"stageNumber": 1,
"http": {
"url": "https://XXXXX/netsuite-rest/igam",
"httpHeaders": {
"Authorization": "${access_token}",
"Accept": "*/*"
},
"httpContentType": "application/json",
"httpParams": {
"type": "user",
"action": "getdetails",
"employee_id": "${response.call1.accountID}" // Ensure this is correctly referencing the id from call1's response
},
"httpMethod": "POST"
},
"inputParams": {
"dependentCall": true
},
"listField": "", // Update this based on the actual JSON path in the response if needed
"keyField": "accountID",
"colsToPropsMap": {
"accountID": "id~#~char",
"customproperty2": "isInactive~#~char",
"customproperty3": "employeetype.refName~#~char",
"customproperty4": "lastModifiedDate~#~char",
"customproperty5": "firstName~#~char",
"customproperty6": "lastName~#~char",
"customproperty7": "middleName~#~char",
"customproperty8": "hireDate~#~char",
"customproperty9": "middleName~#~char", // Duplicate, consider removing or correcting
"customproperty10": "dateCreated~#~char"
}
}
]
}
}
Ensure that placeholders like https://XXXXX/netsuite-rest/igam and ${access_token} are replaced with actual values appropriate for your Oracle NetSuite environment and authentication context. Additionally, verify and adjust the "httpParams" and "colsToPropsMap" based on the exact API documentation and response format
03/27/2024 07:27 PM
@Falcon , This provided json is not working I am not sure how to pass accountID in call2 ? can you suggest any syntax ?
03/27/2024 07:30 PM
Sample JSON
Refer https://docs.saviyntcloud.com/bundle/Dev-Handbook-REST-v24x/page/Content/Developers-Handbook.htm
03/27/2024 08:25 PM
Not working, I tried below json.
03/27/2024 08:35 PM
share logs
03/27/2024 09:19 PM
As confirmed this issue is resolved 🙂
https://forums.saviynt.com/t5/identity-governance/two-level-access-recertification/m-p/84319#M54357
03/27/2024 10:31 PM
Hi @rushikeshvartak , yes I was checking my two forum question at the same time so Instead of here I confirmed this in another forum.
Still we are on access recertification issue. This Rest connector issue has been resolved.
Thanks,
Gaurav
03/27/2024 10:50 PM
Please close this thread
03/28/2024 05:35 AM
What was the exact resolution for this issue? What was missing from the json? What is the final working json for this?