How to set disableOrderingCheck as true using API

[Psantoshi (Pramod Santoshi)]

Hello,

How to set disableOrderingCheck as true for one source application using API?

Also we tried to set Order by clause aggregation query still getting the same error is being displayed.

Error:

[ InvalidConfigurationException ] [ Possible suggestions ] For data merging, data should be ordered. Please add order by clause in aggregation query or set disableOrderingCheck as true. [ Error details ] java.lang.Exception: Data out of order exception. Data should be sorted in ascending order. Last identifier 9 current 14

[amishra97 (Abhinav Mishra)]

1. You can use this API to update the source.

OR

2. You can modify your query like this.

SELECT * FROM Employee ORDER BY ID;

[Karthikeyan_U (Karthikeyan Udhayasurian)]

Hi Pramod,

You can use the update source (https://developer.sailpoint.com/idn/api/v3/update-source/) to update the “disableOrderingCheck” attribute as @amishra97 mentioned. In addition to that you have to make sure your aggregation query uses order by, otherwise you might see data inconsistency.

Example:

[
  {
    "op": "add",
    "path": "/connectorAttributes/disableOrderingCheck",
    "value": true
  }
]

[PramodS (Pramod Santoshi)]

Hi @Karthikeyan_U ,

Below error is being displayed when I try to send the mentioned API,

{
“detailCode”: “400.1 Bad request content”,
“trackingId”: “ba91f5f28574443299903353fa989091”,
“messages”: [
{
“locale”: “en-US”,
“localeOrigin”: “DEFAULT”,
“text”: “The request was syntactically correct but its content is semantically invalid.”
},
{
“locale”: “und”,
“localeOrigin”: “REQUEST”,
“text”: “The request was syntactically correct but its content is semantically invalid.”
}
],
“causes”:
}

[Karthikeyan_U (Karthikeyan Udhayasurian)]

Hi @PramodS ,

There was a small mistake in the payload, use the below payload

[
{
“op”: “add”,
“path”: “/connectorAttributes/disableOrderingCheck”,
“value”: “true”
}
]

[jsosa (Julian Sosa)]

Hi Pramod, besides the PATH call, you can first call the GET call to retrieve your source.

Then, select all response (entire source), and paste it in the PUT call:

Just modify the disableOrderingCheck attribute, and click on send.

[imckenzie (Ian McKenzie)]

Is there any insight to why option 2. does not seem to work? I’ve attempted to order my query results by what the account attribute mapped to “Account ID” (a Primary Key column in query), yet I get the same error displayed when it goes from value “9” → “10”. This is the case in setting the attribute type as either “int” or “string”