Barbara
New Contributor II
Joined 4 years ago
User Profile
User Widgets
Contributions
Filter on Epoch Time
In the flattened data set, $lastUpdatedAt is an Epoch time value (i.e. 1665404233565) A Filter snap is being used to filter out flattened records updated prior to yesterday. There are 64 records in the dataset that meet that condition. When the filter expression is set to $lastUpdatedAt>=Date.parse(Date.now().minusDays(1).toLocaleDateTimeString({“format”:“yyyyMMdd”}),“yyyyMMdd”) all records are filtered out. What filter expression will correctly filter out $lastUpdatedAt Epoch time values greater than zero hundred hours Epoch time yesterday?1.5KViews0likes1CommentHow to Filter in a Non-Ultra Pipeline?
I am new to SnapLogic. I have a requirement to execute a REST snap that will return tens of thousands of nested JSON records and only flatten and export records that were modified yesterday. The Filter snap documentation says it only works in Ultra Pipelines, and the Ultra Pipeline documentation says “Ultra Pipeline tasks are used to implement real-time web service integrations which require expected response times to be close to a few sub seconds.” The REST snap execution will take substantially more than a few sub seconds given the number of records expected. Given that, what do I have to do to meet the requirement to only export flatted JSON records that were updated yesterday?2KViews0likes1CommentPipeline Corrupts For No Reason
I have a pipeline that calls an API, flattens JSON records, outputs a csv file with a .tmp extension, verifies the file was written, then renames the .tmp to .csv. This pipeline is in production. The pipeline was copied and a change was made to one API parameter. It ran fine. When snaps, such as the emails, are enable/disabled, the pipeline fails on the file rename snap because the .tmp file is not found. Another corruption occurred with the changed parameter. The pipeline ran fine, then when attempting to run the same unchanged pipeline the next day, an error that the parameter that was changed wasn’t defined was encountered. Another corruption occurred with the changed parameter. The pipeline ran fine, then when attempting to run the same unchanged pipeline the next day, an error that the parameter that was changed wasn’t defined was encountered. Another corruption occurred in a copy the day after successfully running AFTER NO CHANGE with the MetaAggregator throwing error Failure: Invalid number in the input data at %s, Reason: Character N is neither a decimal digit number, decimal point, nor “e” notation exponential mark., Resolution: Please make sure input data at parseInt(jsonPath($, “metadata[*].entity.paging.count”).toString()) be a number type. Why would this pipeline that is in Production be corrupting so badly and so unpredictably in the Test environment?1.3KViews0likes0CommentsRecommended Approach for Multiple REST Get Snaps
I need to make multiple GET calls to the same API, aggregate and flatten the JSON record, and write one single csv file. Each GET snap execution parameters are the same except for the RecordType, which has six (6) different values. The solution in video “Snaplogic Best Practices: Sub Pipelines and Guaranteed Delivery” at https://www.youtube.com/watch?v=RqjKkG4V354 may be part of the solution. A ForEach pipeline with the list of RecordType values in JSON that is parsed and passed to the subpipeline with the GET snap using ForEach would work. How can the multiple responses from the GET snap pipeline be aggregated so they can be flattened and output into a single csv file?3.8KViews0likes3CommentsSigned Up for Trial, Now Can't Log In with SSO
I signed up for the trial with for training. Two days ago I was granted access to our corporate development environment. When I attempt to connect via SSO, error “SSO login cannot be used for users that are members of orgs that have different identify providers”. I called the support line, which required two calls because the line was so bad. I was instructed to email Support@SnapLogic.com, which I did yesterday. Resent the email this morning as there has yet to be a response. Attempting to use SnapLogic has become very painful. How do I get this issue resolved?3.5KViews1like3Comments