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.
Curious if anyone else has issues with BOX Account not automatically refreshing the token frequently enough, resulting in processes failing because of the expired token?
From Manager → Activity Log → Asset, I can see the system usually updating the a...
Our users authenticate via SSO. When I create a new user, it seems required for them to go through the process of getting the welcome email and manually resetting their password (never to be used again) before the SSO login will work. Am I missing ...
Anyone have an idea what the culpret might be with this “prepare on neighbor” error with the Pipeline Execute snap, excuting a child pipeline on my groundplex?
I get these sometimes, seemingly randomly… Most annoying part is that even though I have...
Looks like OneDrive has some REST APIs as part of some Microsoft Graph APIs, but curious if anyone has had success integrating with OneDrive via SnapLogic?
docs.microsoft.com
Access OneDrive and SharePoint via Microsoft Graph API -...
I opened a ticket with support, but was curious if anyone else has seen this behavior…
I have a pipeline with multiple documents coming out of a Mapper snap to a Pipeline Execute snap, each with different document names.
For troubleshooting this is...
SFTP (FTP over SSH) is just a protocol and doesn’t really matter what kind of system (Windows, Linux, etc.) is on the other end. You can authenticate via user/pass (basic auth) or SSH key.
Sometimes it’s useful to have a parent pipeline that executes a child pipeline and passes some values like these as parameters to the child. Then the child can reference them anytime (_parm) without having to keep passing the value along from one sn...
Documents (records) are generally processed through snaps (including the router) in a streaming fashion, independent of each other. To accomplish what you’re looking for, perhaps you could group all the documents together using one of the group by sn...
An “error pipeline” might not be right for you if you want specific processing for various types of errors that various snaps can give. In my opinion this would be for more generic error handling, and there are usually pretty standard fields ($error...
If you have an error pipeline defined for your base pipeline, then I believe it will always run (and wait for error data) when your base pipeline runs, not only run when there is actually an error. If you have an error path on a snap, then it should...