REST SyncLead Blank vs "NULL" | Community
Skip to main content
V
vladpetrovic
New Participant
October 9, 2022
Solved

REST SyncLead Blank vs "NULL"

  • October 9, 2022
  • 1 reply
  • 1410 views

Hey team,

 

What is the expected behaviour when updating a lead using the REST SyncLead API (Non Bulk) and passing an empty/blank value? I was under the impression that a blank/null value for a field would ignore the current value of field while passing a string of "NULL" would clear the field.

 

Is that correct?

 

Thank you,

Vlad

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by SanfordWhiteman

You're thinking of forms and flow steps, where because there's no ability to specify an actual null (form values are strings) the string "NULL" is a reserved word that means "set to empty".

This behavior doesn't exist with the REST API because it doesn't need to. JSON explicitly supports null.

1 reply

SanfordWhiteman
SanfordWhitemanAccepted solution
New Participant
October 9, 2022

You're thinking of forms and flow steps, where because there's no ability to specify an actual null (form values are strings) the string "NULL" is a reserved word that means "set to empty".

This behavior doesn't exist with the REST API because it doesn't need to. JSON explicitly supports null.

Terms & ConditionsAccessibility statement

Loading footer...