Existing implementation to workaround the issue.
// Take care of null and missing values encountered during deserialization
var settings = new JsonSerializerSettings
{
NullValueHandling = NullValueHandling.Ignore,
MissingMemberHandling = MissingMemberHandling.Ignore
};
var jsonString = responseMessage.Content.ReadAsStringAsync().Result;
return JsonConvert.DeserializeObject<MyObject>(jsonString, settings);
The existing WebServiceUtils does not have the ability to add JsonSerializerSettings to assist with different object mappings coming back