Actually files can be read from a pipeline in a different project than the file being read, and does not need to be in the shared folder.
If you have the full absolute path/ accurate relative path to the file you are trying to read then there is nothing preventing you from doing so. However the File Reader snap will only recommend paths to files in the same project or files in the shared folder. Screen shot below shows an example of a pipeline reading a file from a different project, not in the shared folder, and how this is achieved. In this case the pipeline is in project ExpressionTester/shared and reading from a file in projects/alpha
Thank you @cjhoward18, but does it not require permission at the project folder level wherein we provide read, write, execute, owner or full access permissions. I thought by default we don’t give read permission across project folders more out of security.
Yes, your right there are ways to restrict access rights for users over a certain project, so they would need to have access to both projects.
Thank you all. I used the absolute path and was able to access the csv file. Also, write to another project.
