Errors from IFS
Page will include specific errors returned by IFS that has been identified so far, what they mean and how to handle them.
Last updated
Was this helpful?
Page will include specific errors returned by IFS that has been identified so far, what they mean and how to handle them.
Last updated
Was this helpful?
This error indicates that the IFS API is expecting additional parameter(s) in request header. Inspect the request header contents in Chrome inspect log and add required header attributes. Finding out what attribute is missing is solved by the "trial and error" method.
In case more than one additional header attribute needs to be added, create a Flow table table(Name, Value) and provide values and use in the machine step as in the example.
Rest call header does not include "Content-Type" value "application-json" or body is not correctly in json format. Normally occurs when you call IFS outside flow apps (like Postman).
To improve the response time, the IFS OData Provider caches the projection metadata once it is loaded from the database. During each call OData Provider validates the cached metadata version with that of the database. If the validation fails, the request will fail with HTTP response code 500 and the response body will contain the error code as MI_MODIFIED_ERROR. Then OData-Provider will invalidate the cached metadata, forcing it to be fetched from the database at the next request.
When a user gets this error response the OData-Provider expect the user to retry the same request again. Then OData-Provider will load the latest projection metadata from the database and serve the request accordingly.
Error occurs when you execute Ready by Key -operation with an non-existent entity key.
Error Indicates that API specification exists but implementation is missing. Select another operation.
The error in this example occurred during Update-operation which requires if-match attribute. Read more about solving this issue.
