Which IIQ version are you inquiring about?
8.5
Please share any images or screenshots, if relevant.
Configured Delta aggregation in WS connector in IIQ for fetching profiles from NERM, based on last successful aggregation timestamp from Application XML.
getProfiles API returns HTTP 400 whenever no profiles exists under the timeframe ( if no updates found on profiles from NERM end).
However, in SailPoint IIQ end:
HTTP 400 is treated as a hard failure, which causes the WS operation and aggregation/account fetch to fail, even though “no profiles found” is actually a valid business condition (not an error).
trying to handle in WS AfterRule by adding 400 as success code, but still facing issue with attribute path.
Please provide insights to handle this 400 NERM bad request in IIQ.
Thanks,
Sakthi