DisableOptimization not working on Account Aggregation API in Workflows

Identity Security Cloud (ISC) ISC Discussion and Questions
, , ,
1

Hello,

I am building a workflow that will run disabled optimization Account Aggregations on specific sources, but for some reason the disableOptimization is not working. I’ve tried putting it in the request body, I’ve put it as a query parameter, and I’ve even tried putting it directly in the URL as a parameter. All scenarios still result in the aggregation running with optimization enabled.

The Documentation for this API places the disableOptimization in the request body, but when I try to do the same via Thunder Client, I keep getting a 500 error. When I place the disableOptimization as a query parameter and set the value to true, I get a 202 response in Thunder Client and the aggregation shows in our tenant with optimization disabled. I’m just not able to get this same behavior when running the API via workflows, it always shows the aggregation as optimization enabled.

Has anyone else run into this or is there a known issue with this specific functionality? Any help is appreciated, thank you!

2

can you post you calls here? for both cases.

3

@lampard08 This is the request from the workflow

image
image1014×2117 101 KB

And this is the one from Thunder Client that gives me the 202 response when I use disableOptimization as a query parameter

image
image2188×1053 112 KB

4

Try adding ‘Content-Type’: ‘multipart/form-data’, as header.

headers = {
‘Content-Type’: ‘multipart/form-data’,
‘Accept’: ‘application/json’,
‘Authorization’: ‘Bearer ’
}

Reference : import-accounts | SailPoint Developer Community

5

try “request content type” to text in your workflow. and disableOptimization : true should be in body not request parameter.

6

@lampard08 I did both of those things and the aggregation ran with optimization enabled still. I mentioned in the post that the only way I’ve been able to get the aggregation to run with it disabled is by putting it as a query parameter in Thunder Client, so that’s why it’s a parameter in the screenshot.

7

This did not work, still ran with optimization enabled unfortunately.

8

I ended up figuring it out! When you select ‘Form’ in the request content type, it gives you key-value pair format for the request body. I put the disableOptimization as true in the key-value and it worked.

@lampard08 @rahulks88 Thank you both for your responses, I appreciate it!