SOLVED

REST SyncLead Blank vs "NULL"

Go to solution
vladpetrovic
Level 1

REST SyncLead Blank vs "NULL"

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

1 ACCEPTED SOLUTION

Accepted Solutions
SanfordWhiteman
Level 10 - Community Moderator

Re: REST SyncLead Blank vs "NULL"

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.

View solution in original post

1 REPLY 1
SanfordWhiteman
Level 10 - Community Moderator

Re: REST SyncLead Blank vs "NULL"

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.