You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Intricacies with OIC XSLT Mapper

Accepted answer
34
Views
10
Comments
edited Apr 17, 2024 2:40PM in Integration 10 comments



Summary:

We have an OIC integration that calls Concur REST API to do user provisioning and de-provisioning. I run into an issue that doesn't make sense at all during "rehiring logic".
There is a PATCH Operation that we can call to "re-activated" user account in Concur.

In POSTMAN client, it worked just fine.

Sample Payload of Request Body (in POSTMAN)


Here is my OIC Mapper and Yes I have tried many different combination of passing "null" values to the terminationDate Schema. (Including explicitly setting null as the value)


For unknown reasons, when I execute this OIC integration (Screenshot because the formatting on this is horrifying), following error message is throwing on Concur side.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!