Sure @ptaylor, I can share some snaps but it will take some time as I have to replicate the pipeline and disable the Salesforce snaps. Reason being; we have a workaround as mentioned earlier on changing the snap execution to “Execute Only” and just executing the pipeline instead of saving/validating pipeline. Also, currently we are testing it and dev has been marked complete so I will have to branch out the pipeline in such a way that it doesn’t affect the ongoing testing and dev that has been marked complete.
You had a valid point on datatype; where one could be a number and other would be a string, I double checked this morning as I wasn’t confident whether it was string vs number for this pipeline and the data type is string so we are covered in there. I’ll share the snaps as soon as I’m able to.
Appreciate your patience and help on this one.
@ptaylor, I have observed this behavior again where saving a pipeline even though the Salesforce snaps’ settings were “Execute Only”, ingested Null values to Salesforce.
[Q-1]: Would Salesforce upsert snap insert/update records while saving a pipeline even though its snap execution has been set to “Execute Only”
[Q-2]: Why would Joins output Null data when we clearly know that the data IS NOT NULL? Again this happened during saving a pipeline, I forgot to disable the salesforce upsert snap while making a minute change in other snap and 2k records have been affected now ☹️
