cancel
Showing results for 
Search instead for 
Did you mean: 

Ability to differentiate between null and undefined in Common Data Service "Update a Record"

In the CDS "Update a record" filling in the fields that need to be updated, I have a situation where I am mapping from fields in a JSON from another source.  

In this case for one Dynamics 365 field being updated by CDS, either:

The value exists in the other JSON and is not null (meaning update the existing field in Dynamics)

The value exists in the other JSON and is null (meaning clear the existing field in Dynamics) or

The value doesn't exist in the other JSON (meaning leave the existing field alone in Dynamics.

 

Currently there is no way to differentiate between the last 2 cases with a massively complicated set of if statements. I would like to be able to use the CDS update a record connector and, for any field, pass in either the new value, null (to clear the field) or empty (to leave the field alone).

Status: New