This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Created by @dwhite
An example of how to perform a dynamic pivot on data that needs to be pivoted. The traditional Pivot Snap is static and has to be configured per set of data (Ex. in pipeline). This pipeline shows how one can perform a pivot operat...
Created by @dwhite
A sample pattern one could use to trigger a large data orchestration process with several steps (synchronous and parallel) that has an asynchronous response at the start so the calling process will not wait. Response contains a Sn...
Created by @dwhite
Enter a base DN and an AD username to use LDAP search to find a specific user. Run as a trigger task endpoint or as a child pipeline.
Configuration
Enter the base dn to look for users in via the “baseDn” parameter. Enter the AD ...
If you’re having problems with XML validation going in or out of XML (formatter/parser) or if you wish to validate a binary XML without parsing it so save execution time you can use the XSLT snap to do this validation.
XSLT snap takes a binary input ...
For ultra, this is all you need to work with headers, content, and url parameters.
Accessing a URL parameter from an Input request. All url parameters passed on the call in must be accessed in the incoming document and not like a traditional trigger....
If I had to guess I’d say it was the cookie. Postman is auto-sending this for you because it is stateful probably captured it in the return of your first API call.
In SnapLogic, each of the snaps execute separately, even if you have a chain of rest s...
Could you expand that temporary headers section in postman in the request header section? What kind of authorization are you using in both postman and SL?
Also, have you checked the endpoint to see if the file from the SL post made it there regardles...
Looks like you’re giving the entity JSON, a target server expecting form-data isn’t going to know what to do with that. Try formatting your entity like
‘key1=’ + $yourData1 + ‘&key2=’ + $yourdata2
Do it right in the entity setting of the snap.
Also, ...
Replace your two scripts with mappers should net you some performance gain. You don’t need to use a script to make a string of json.
Script in “Split events” pipeline which is doing
data = self.input.next()
newData = {}
newData[‘record’] = data
newDa...
