Try with this expression:
$.mapKeys((value, key)=>key.endsWith('__c') ? key.replace('__c','').toLowerCase() :key.toLowerCase()).mapValues((value, key) => key.toLowerCase().search("createddate") >=0 && value !=null ? Date.parse(value).toLocaleDateTimeString({"format":"yyyymmdd"}) :value) @Henchway - Error pipeline is useful for normal ETL scenario but for exposing APIs you can follow the traditional approach, take error view out and union all your error and success flow as final response.
I have also tried but not found the solution.
@dmiller Do you have any other solution for this scenario?
Thank you, that’s what i’ve been doing.
Now the issue is that it won’t fit a unified error/transaction logging approach, but i suppose we’ll have to come up with a new one there.
Best regards
Thomas
I’ll check with out Professional Services team to see if they’ve encountered it.
Script snap with ultra pipelines: original property mapping to doc which is modified | SnapLogic - Integration Nation - 12415
