03-22-2018 02:48 PM
The following patterns migrate assets from one project to another in the same org. These patterns make use of the SnapLogic Metadata Snaps.
Source: Existing accounts, files, and pipelines within SnapLogic
Target: A second project within SnapLogic
Snaps used: SnapLogic Metadata Snaps, Mapper,
09-10-2018 07:47 AM
How can we migrate files between orgs without using the Migrate function on the project in Manager? I have tried various methods to read/delete/browse/write files in the source and target orgs with and without accounts that have full access to the source and target orgs. But the files can only be seen by snaps and in Manager when the snap that creates or reads them is executed in the same org. The files can be successfully written by the source org into the target org but snaps executing in the target org cannot see them and vice versa. (Permissions cannot be set on SLDB files by the File Writer snap.) Nothing is working unless I create separate pipelines and tasks for each function (Directory Browser, File Writer) on the target org and call those from the source org with the Rest POST snap so that they are executed on the target org. This seems extremely complicated for a seemingly simple task of deploying files. What am I missing?
09-24-2018 04:54 AM
Thanks so much @dmiller.
We’re also interested in the following patterns:
Thanks!
09-24-2018 10:12 AM
@omair, I’m asking Dev about the first request to see if it’s possible.
Regarding creating a user-specified project or project space, do you mean a project other than the project created when the user is first created?
03-21-2020 09:02 PM
Hello,
Is it possible to rename a project space or folder using metadata update snap?