ServiceNow Scripted REST APIs: Part 9 - PUT and PATCH

This video implements a PATCH resource for modifying records in ServiceNow. It also discusses the difference between PUT and PATCH, and how these relate to the GlideRecord.update() method.
Scripts in this series are located in my GitHub repo: github.com/Jay...
Further learning
• PUT Method for HTTP: www.rfc-editor...
• PATCH Method for HTTP: www.rfc-editor...

[@evrenc.2874]

Thanks a lot for video

[@tomasito19861]

Hi Jason, first of all, thank you very much for the whole series of this REST API training. I think your videos should be in the official credential program of ServiceNow for this topic. But....my question is, why we didn't have to convert {vin} to string in GET single vehicle rest API and here we did? Thank you

[@sridharmamilla1]

Nice and simple...👍

[@marshallmoyo4505]

"The main difference between PUT and PATCH in REST API is that PUT handles updates by replacing the entire entity, while PATCH only updates the fields that you give it. If you use the PUT method, the entire entity will get updated. In most REST APIs, this means it will overwrite any missing fields to null."

[@secretaryofsimplification]

This is a behavior (null values inserted when using PUT with ServiceNow REST APIs) that I have not noticed. Have you seen this occur?