โ07-15-2022 01:18 PM
Hi Team,
Lately, I observed distinct results getting generated during compile time (i.e. saving a pipeline) vs run time (i.e. executing a pipeline). Has anyone observed this behavior?
For instance, consider a simple example of reading a flat file, doing some transformations, using joins and exporting it as a csv/excel file. When we save the pipeline and the Snap Execution
has been set to Validate & Execute, a flat file will be generated in Manager with default 50 records (this may be ranging from 1-2000 depending on each userโs preview count settings). The file generated during saving a pipeline is different than one generated after executing a pipeline.
What I observed was, the joins didnโt work during compile time whereas they worked during run time.
My use case doesnโt need to export a file but to update new records in Salesforce, whatโs happening over here is that, during compile time, a vital field data is going blank and while running the pipeline, the data is going as is. The concern here is "As I'm considering brand new records ONLY "
, compile time execution ingests wrong data and run time wouldnโt be able to ingest the correct data as the record was already ingested (new fields only, run time wouldnโt fetch that data as itโs no longer a new record)
Any help/thoughts on this would be highly appreciated.
Thanks!
Best Regards,
Darsh
โ07-18-2022 03:45 PM
Tagging the experts to get some help on this one.
โ07-18-2022 04:09 PM
I defer to the developers on this one. I avoid Validate and Execute.
โ07-18-2022 04:13 PM
Sorry, Iโm finding this a very confusing post.
Is that related to the paragraph before it or the one after it? Iโm not seeing anything else about joins.
What do you mean by โgoing blankโ? Whatโs supplying that data?
We need more context to make sense of this. Whatโs a brand new record? From where? It sounds like you might want to change the snap that updates Salesforce to Execute only
so that validation doesnโt perform updates that you only want to happen during execution.
Please use โvalidateโ and โexecuteโ, not โcompileโ and โrunโ. Thereโs nothing in SnapLogic thatโs really equivalent to โcompilingโ so thatโs a confusing term.
โ07-18-2022 04:58 PM
Sincere apologies @ptaylor for the confusion. How I understand the 3 buttons on snapLogic is as below:
I will not use Compile and Run time to avoid confusion henceforth. Let me explain again what the issue is and what Iโm trying to achieve.
Upstream system: Snowflake
Downstream system: Salesforce
Issue: Data is different in output preview of a snap when the pipeline is saved or validated. I did a sanity test and the ID record (i.e. col A) that should have some data (i.e. in col H) is coming as โNullโ values. This data that Iโm expecting is coming from Joins though.
The above behavior is not the same when the pipeline is executed. With execution in place, the data comes as expected.
Definition of brand new records: With the help of Inner Join, Iโm considering IDs from snowflake that are not in Salesforce and Iโm ingesting those NEW records to Salesforce with this pipeline.
Salesforce Create and Salesforce Update doesnโt work efficiently (from what Iโve observed) so Iโve been using Salesforce Upsert for this operation.
The concerning piece is that, the last snap of my pipeline is a Salesforce Upsert with snap execution as โValidate & Executeโ; whenever I make some minute changes and save my pipeline, those changes flow to downstream system (i.e. Salesforce) and thatโs an expected behavior however with Saving/Validating pipeline, the data is NOT consistent for the joins (as explained before) and this inserts the records (if new record) or updates the record (if existing record) as we are using an Upsert.
When the pipeline is executed, the same record wonโt be inserted as itโs no longer a NEW record and it wonโt be updated too as that record hasnโt received any update from the upstream systems. This is basically the data snapLogic should have calculated during saving/validating pipeline but it wasnโt able to!
What Iโm trying to achieve: Consistent data flow from Snowflake to Salesforce (with the help of Joins as those would be needed anyhow)
Happy to clarify further questions if any!
Solution: For now, Iโve already changed my Salesforce Upsert snapโs settings to โExecute ONLYโ so that even when I save/validate my pipeline, those updates donโt flow downstream. I would have expected joins to work in all the different scenarios like save/validate/execute. Is this a limitation of the tool or am I doing something wrong over here? I wouldnโt be surprised if Iโm missing a crucial step, Iโm still learning snapLogic so by all means, feel free to give me right directions (I wouldnโt be offended).
Apologies again for the confusion and looking forward to your thoughts on this one.
Best Regards,
Darsh