Transformation rules inside mapper snap not exported to output file

Hi Team,

I have found one of the transformational rules applied on “date field” not getting exported to the final output file (i.e. excel file) when the pipeline has been executed.
Output preview on the snap does show the right data (i.e. expected one), pipeline validation also shows the right data however the file which gets generated after pipeline execution doesn’t get those details.

I have tried the following:

  • validated pipeline via shift+validate
  • tweak the transformation rule, save the pipeline and check the output in the preview
  • validated the preview file (with default 50 records)
  • deleted the file generated by “validate & execute” snap on File writer with default 50 records so that new instance of data comes in
  • executed the pipeline with different file name multiple times

It’s a simple pipeline consisting of

            Snowflake Execute --> Mapper --> Excel Formatter --> File Writer

Sharing some screenshots to help it understand better:
(1) Pipeline with 4 snaps

(2) Snowflake execute output preview in JSON format (highlighted yellow fields needs transformation)

(3) Transformation Rules on Date fields

(4) Transformation Rule: $Expire_Date.toString().replace('{Timestamp=',"").replace('.000+0000}',"Z")

(5) Output preview after transformational rule

(6) Mapper output preview shows different data

→ I’ve observed certain times that the transformation rules won’t work so I go inside the mapper, modify the rule a bit, bring it back to default rule so that I can save it (save is not enabled if there is no change thus this workaround)

(7) As shift+validate didn’t work, had to change the transformation rule, save it and then this is the output preview on mapper snap:

(8) Settings under excel formatter snap for reference:

(9) Settings under File Writer snap for reference:

(10) File generated with default 50 records due to validate & execute on File writer snap

(11) Downloaded the file that gets generated in step 10 and below is the output (expected)

(12) Executed Pipeline

(13) Output File of Executed pipeline

I’ve seen this happening numerous times particularly to fields containing timestamp in other pipelines too, am I doing something wrong over here? Any settings that needs to be changed either in Mapper, Excel Formatter or File Writer snap?

Thanking in advance for your valuable time and suggestions on this one.

Best Regards,

Hi @darshthakkar,

Since the field you are transforming is a timestamp ( datetime ), it is a best practice to transform the date and format it with the built-in method .toLocaleDateTimeString({format: "yyyy-MM-dd'T'HH:mm:ss'Z'"}) instead of converting it to string and then manually replacing the timezone offset.


Thank you @j.angelevski for the direction.
I will try your suggestion and keep you posted on how it goes, appreciate your help though!

Rationale behind converting it to String was: I wanted to export the raw data and it didn’t allow, error was “Flatten the file before export” thus .toString() was used. I wasn’t aware of the built-in method so THANK YOU for sharing that.

With the above approach, the result in Date is coming as “Null”

Screenshots below for reference:

@darshthakkar try

Date.parse($Expire_Date.Timestamp).toLocaleDateTimeString({format: "yyyy-MM-dd'T'HH:mm:ss'Z'"})

I believe that will do what you want

1 Like

This worked! Thank you, Robin.

However, the exported file has no values under dates, screenshot below for your convenience:

Just for my understanding, why would the Expire_Date not give us the same results? Is it because it’s an object vs Expire_Date.Timestamp a string? (Q-1)

Moreover, $Expire_Date.toString().replace('{Timestamp=',"").replace('.000+0000}',"Z") did give us the expected results during output preview of the snap and after validating the pipeline however the transformation didn’t work when the pipeline was executed, what would be the rationale behind it? (Q-2)

I want to understand this in details so that I can learn snapLogic in a better fashion and be a good snapLogic developer. Please don’t get me wrong.

Best Regards,

In addition to this,

Output preview is different on the field and mapper snap, screenshots below:


Isn’t this strange as the same snap which shows a preview as expected output in one of the fields shows a null when doing a sanity check on the entire snap.

Providing a summary of the transformational rules applied so far:

1. $Expire_Date.toString().replace('{Timestamp=',"").replace('.000+0000}',"Z") → Output Preview [works expected] → Exported Excel File [transformation rules don’t appear to work]

2. $Expire_Date.toLocaleDateTimeString({format: "yyyy-MM-dd'T'HH:mm:ss'Z'"}) → Output Preview [shows Null values] → Exported Excel File [all blank values]

3. Date.parse($Expire_Date.Timestamp).toLocaleDateTimeString({format: "yyyy-MM-dd'T'HH:mm:ss'Z'"}) → Output preview [works expected] → Exported Excel File [all blank values]

I’ve tested the above transformational rules with csv file and the results are the same as discussed above

Output preview file generated in “Manager” if the File Writer snap has Validate & Execute enabled shows the expected data with both excel and csv versions of file but shows blank when the file has been downloaded after executing the pipeline, this blows me away on why would it behave like this?

That’s very odd indeed. Let me look into it a bit to see what is happening.

1 Like

@darshthakkar You can check the setup of excel formatter. But I would suggest go with CSV formatter rather excel formatter , and create file with .csv extension.


Thank you, @Supratim for the suggestion.
If you check my previous responses, I’ve tried both with excel and csv formatter and it doesn’t work. I’ve also shared the screenshots of excel formatter in my first comment which can be accessed here

Moreover, I want an excel file and not csv.

The Snowflake snaps have a setting called Handle Timestamp and Date Time Data. Unfortunately, its default setting, Default Date Time format in UTC Time Zone, has less-than-ideal behavior. The object type of the timestamp objects is java.sql.Timestamp, which will result in the odd inconsistencies you’re seeing between validation vs execution, and it’s also not a very usable type on the SnapLogic expression language.

I suggest changing this setting to the other option, SnapLogic Date Time format in Regional Time Zone. This will convert the timestamps to the type org.joda.time.DateTime, the type that the SnapLogic EL functions are designed to deal with.

This option will also produce a DateTime with the default time zone of the plex node, which can complicate things if the node’s default timezone isn’t UTC. But based on what you’ve shown, your node’s default timezone is UTC, so this shouldn’t be a problem for you, fortunately.

After changing that setting, try using an expression like $Expire_Date.toLocaleDateTimeString({format: "yyyy-MM-dd'T'HH:mm:ss'Z'"}).

Hope that helps.

1 Like

Hi @ptaylor,

Really appreciate you helping me on this one however the values are coming out as Null with the solution provided. Screenshots below for your reference and convenience:

(1) Snowflake Execute snap settings changed:

(2) Values coming as Null during output preview

(3) Output preview of the mapper snap in JSON format

(4) Validation file generated with default 50 records:

(5) File generated after executing the pipeline


Though there is one positive of this solution, my original transformation rule is working fine, not sure if its intermittent as I’ve observed that rule working fine at some instances and after a while, it will go berserk.

Let me know your thoughts on this.

Best Regards,

It looks like you’re missing a $ at the beginning of the expression. Please check.

1 Like

Did adding the $ at the beginning of your expression help?

Allow me to explain a bit more about validation vs execution. This will be generally useful in your use of SnapLogic.

When you validate a pipeline, the SnapLogic platform will cache the preview output of each snap. On the next “regular” validation, it considers which snaps have been modified since the last validation, and will reuse the cached output of all snaps up until the first snap that was modified. It does this as an optimization to avoid re-executing potentially costly or time-consuming operations like Snowflake Execute. So when you’re modifying the Mapper and a new validation occurs, it’s operating on the cached preview data from the Snowflake Execute.

Usually, that invisible use of cached data during validation is a good thing. It makes designing pipelines faster by re-running only the modified snaps and the snaps downstream from those. Usually the results are consistent whether you’re validating with cached data or executing.

However, as you’ve witnessed, there can be subtle issues that arise from the use of cached data. This is because the caching mechanism is based on serializing the preview data to JSON format and then deserializing it when the cached data is used. JSON only has a few basic data types, which don’t include types like dates and timestamps. So if an output document uses objects of types that don’t correspond to native JSON types, SnapLogic will represent those objects using a custom JSON representation. For well-supported types like Joda DateTime, it will use a representation like this where the type key begins with “snaptype”:

{"_snaptype_datetime": "2022-03-14T15:24:24.974 -06:00"}

When the platform deserializes the JSON representation of the output document and encounters that object, it’s able to correctly restore a Joda DateTime object identical to the one that was serialized, so the downstream snaps will behave consistently regardless of whether cached data is used.

Unfortunately, some object types like java.sql.Timestamp are not well-supported by the serialization/deserialization of the caching mechanism, resulting in inconsistent behavior. This is the type used for timestamps when the Snowflake Execute’s “Handle…” setting is “Default Date Time Format…”. The serialized representation looks like this:

{"Timestamp": "2022-03-14T21:24:24.974+0000"}

Unfortunately, the platform does not know how to deserialize this cached representation to restore an identical java.sql.Timestamp object that was serialized. Instead, it will deserialize this as a Map containing a single key/value pair, exactly as shown in the JSON. So your transformations that depended on the presence of “Timestamp=” in the toString() representation or on the .Timestamp sub-object were relying on the mis-deserialized cached preview data and would only work in that context.

You can force all snaps to re-run during a validation (avoiding any cached data) by either holding Shift as you click the validate icon, or by clicking the Retry link next to “Validation completed” if that link is displayed. But it’s better to avoid the issue by configuring the snap to use the data types that are well-supported for caching.

Hope that helps.

1 Like

It worked, thanks a ton @ptaylor for your solution and attention to detail.
A quick question on which rule would you recommend to use as both the below-mentioned are working as expected (SnapLogic Date Time format in Regional Time Zone has been selected under snap Settings)

(1) $Expire_Date.toString().replace('{Timestamp=',"").replace('.000Z',"Z")

(2) $Expire_Date.toLocaleDateTimeString({format: "yyyy-MM-dd'T'HH:mm:ss'Z'"})

This is super helpful, thanks a ton @ptaylor for sharing this information. I did try with Shift+Validate but the results were inconsistent. That was my first comment while raising this question:

I believe it’s in the best interest to use the data types that are supported for caching as the results are consistent with this approach.

That expression works because of the second replace. You don’t actually need the first replace because the string won’t contain Timestamp= as I explained. So this simplified expression would also work:


1 Like


My bad for writing multiple .replace statement as when I saw the preview inside the mapper snap against that field (i.e. $Start_Date and $End_Date), it showed me {Timestamp=' (I believe this is exactly what you explained in detail regarding caching)

@ptaylor: Would it be best practice to use $Expire_Date.toString().replace('.000Z',"Z") or $Expire_Date.toLocaleDateTimeString({format: "yyyy-MM-dd'T'HH:mm:ss'Z'"}) or both of the afore-mentioned?

Trying to learn the best practice so that I’m a good snapLogic developer and I can share the same knowledge to others!