Incident not updating when the payload is hitting for resolved case

[mansigoel]

We are using Lexmark integration with SN, basically we have created a transform map which is helping in mapping the fields (the fields which are being sent in the payload to the incident fields)

So, when the same payload is being hit using lexmark - 

{

      "u_incstate": "Resolved",

      "u_resolution_note": "Lexmark Status : Completed , \\r\\nDetails:  Lexmark Case is Completed,\\r\\nResolution Notes: Test Resolution Notes. Phonefix scenario",

      "u_resolution_code": "Solved (Permanently)",

      "u_number": "INC0871705",

      "u_lxm_ticket_number": "CAS-3404534-W4L8Z7"

}

It is not updating the state as "resolved", it is throwing the error every time - Data Policy Exception:
The following fields are mandatory: Resolution code

Although resolution code is already being sent in the payload.

But, when I am trying to use the same service account credentials which Lexmark team is using, and trying to send from postman, it is working as expected.

Can someone please help in this?

[Ankur Bawiskar]

@mansigoel 

how have you configured the field maps for both the resolution code and resolution notes field?

It's strange from postman it's working but not from the actual API

1) Did you check when the actual API is consumed, data is loaded into staging table properly or not?

2) what's the comparison between the actual Lexmark API consumption and postman? both using same endpoints?

3) choice values are matched correctly?

4) From postman are you consuming import set API or table API

If my response helped please mark it correct and close the thread so that it benefits future readers.

[mansigoel]

Hello Ankur,

Yes, I have configured field maps for both resolution code and notes.

1. The resolution notes is being captured in the staging table but resolution code isnt.

2.  what's the comparison between the actual Lexmark API consumption and postman? both using same endpoints? ---- both are just same, using the same endpoints.

3. Choices are the same , and is being matched.

4. From postman are you consuming import set API or table API --- the import set API which is same as we have given to lexmark.