Can you please show us some screenshots? I’d like to see screenshots showing:
The pipeline.
The configuration settings of the Join.
The Pipeline Validation Statistics, particularly the Join.
The Pipeline Execution Statistics, particularly the Join.
Ideally, some preview data for the inputs and output of the Join in a case where it didn’t work correctly, at least showing a particular pair of records that should have been joined correctly and the output record where you’re seeing nulls instead of the values from the input records.
Also, please Download the actual data from these previews and save the json. There may be a subtle difference in the data type of the values for the field that you’re joining on that may become more evident if we can see the JSON (e.g. maybe it’s the string “100” in one and the number 100 in the other).
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 ☹️
