REST API Lead Change Results with NULL Field Values | Community
Skip to main content
A
Anonymous
September 2, 2017
Solved

REST API Lead Change Results with NULL Field Values

  • September 2, 2017
  • 1 reply
  • 3935 views

Hey Nation,

I'm developing an application based on lead changes, and I noticed that, at least when querying the API for changes to leads' leadStatus, I get a number of lead change records where the 'fields' leaf is NULL. I have confirmed, via lead activity logs, that there are no lead status changes that correspond with the time stamps for these leads' NULL field changes. That said, can someone help me understand why I even get lead change records for queries specific to leadStatus?

I ask not to complain, but to help me make my app more robust and/or more intelligent. It's possible that knowing the range of potential reasons for time-stamped NULL results from lead change queries would provide an extra layer of intelligence for my application.

Thank you, in advance, for any insights you can share!

-JC

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

Check for conversion and merge events on the SFDC side.

1 reply

SanfordWhiteman
SanfordWhitemanAccepted solution
New Participant
September 3, 2017

Check for conversion and merge events on the SFDC side.

A
Anonymous
September 3, 2017

Ah, ok. Thanks, Sanford.

Yeah, I do recall seeing some of those occurring at around the same times as the NULL field changes. That said, would you say that this is Marketo's way of saying, "just in case... here are other changes we can't easily categorize"?

-JC

SanfordWhiteman
SanfordWhiteman
New Participant
September 3, 2017

Yep, that's a good way to put it.

Terms & ConditionsAccessibility statement

Loading footer...