It does a bit however I specified before that during validating/saving a pipeline, say for instance, ID = 100 will display Phone Number as “Null” and during pipeline execution, it will display Phone Number as 123456.
As I had access to upstream systems, I knew ID=100 has a phone number 123456 (this is achieved via Join in snapLogic) but I don’t get this while validating my pipeline. If ID=100 wasn’t available in the output preview, I would have been fine with that considering it didn’t come in the first 50 records however it shows ID=100 and Phone Number = “Null”; this is concerning for me!
Moreover, as the Join didn’t work as expected, ID=100 inserted a new record in Salesforce (as ID=100 was a new record) with Phone number = “Null” (when the pipeline was validated as Salesforce Upsert had its snap execution set to Validate & Execute) and this is a weird behavior in my honest opinion. The same has been observed while saving a pipeline if snap execution is Validate & Execute.
I wouldn’t have realized this as I wasn’t checking the output preview but when I validated the records in Salesforce, I was seeing a lot of “Null” values, that made me go to the upstream system, randomly pick up 10 IDs and check their values. To my surprise, those IDs had some data and still were going as Null. After investigating, I came to a conclusion that minute changes in the pipeline and then saving it is causing the issue, thus I quickly disabled the salesforce upsert snap, made all the relevant changes, changed snap execution of Salesforce Upsert to Execute ONLY from Validate & Execute. I still disable the Salesforce Upsert whenever the requirement changes and I have to modify my pipeline as I feel that Joins are not functioning during validating/saving pipeline but they do during executing pipeline (which is a bit absurd)
So in the output of the Join, the Phone Number you’re expecting is null. Do you see the correct value of this Phone Number in one of the inputs to the Join? The preview will show you all the input data so you be able to see what should be correctly joined. Can you see specific input records that should have been joined but weren’t?
Yes, that’s correct. The phone number I’m expecting for an ID (based on the data in the upstream systems) comes as NULL. This behavior is intermittent, at times, output preview of Join will fetch the expected data, other times it won’t. As there are multiple joins on my pipeline, the final mapper where I rename the cols to ingest into Salesforce doesn’t include the fetched data from Join even though Output preview of Join displayed something.
Yes, I do see the correct value of Phone Number in one of the inputs to the Join.
Yes, I do see specific input records that should have been joined but outputting Null values. Reiterating this, this happens in saving/validating pipeline NOT with pipeline execution. With pipeline execution, it works as expected.
As the phone number value from Joins are coming out as Null during saving/validating pipeline, it ingests (inputs) those to the next snap i.e. Salesforce Upsert (as the snap execution was set to Validate & Execute)
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.
