BTW Maybe this is variable, or can be avoided in some way, but it is a good idea to determine where the files are wanted, and what space you can use.
For example, at least with reltio’s implementation, you are limited to something like 100K. I might be wrong, and it may be 100M, but these days you are likely to exceed EITHER!
I ended up using MY ORGS shared folder for files, and that was only for SMALL files that were a good deal smaller than even 100K. The actual sources varied, but some were FTP files that I moved to S3 and read from there. If I had to write out “flat” files, INCLUDING REPORTS, I did THOSE to S3 also. Some of those files are over 100GB.
ALSO, watch out on shared folders. It looks like you only have two, so as long as the pipeline is in a folder underneath the projects fold, and you still only have two levels like that, for local files, you can put the file under …/shared/filename, with “filename” being what you want to call the file. THEN, your file will always be in the shared folder right under projects. REMEMBER though, make sure the admin and user are OK with that, and you don’t exceed a quota.
ANOTHER thing, just so you know. White space, like that on the reader in your picture, indicates the snap isn’t connected. So if you aren’t getting any data, that is why. One neat feature SnapLogic just added, in the last release that you should have already, is an option to disable a snap. It does the SAME thing as idsconnection, but:
- Disables the snap.
- Puts a red circle with a slash through it, to be more obvious
- Is FAR easier to set and reset.
It is under the execute options for the snap. Instead of an enable preview option, it has a list. “RUN”,“RUN&PREVIEW”,“DISABLE”…