Creating project using Metadata SnapLogic Create snap

[mohamadelmardin]

At GameStop we are leveraging a custom solution/pipeline to handle code migration and deployment from one environment to another. We are using Metadata List snap to list projects, accounts, pipelines, tasks from source project then using Metadata Create snap to recreate them in target environment (by specifying org/projectspace/project information). This solution seems to be working fine for all asset types: Account, Pipeline, Task. However it is failing for asset type PROJECT where I am always getting the same error: Error creating asset /GameStop/projects/TargetProject, Reason: Absolute path required when I try to create a any new project.

Did anyone stumble upon that error before: Absolute path required ?? I know that I am using the right absolute path correctly because it is working fine for other asset type: Account, Task, Pipelines. So why I cannot use it to create target project?

[sriram]

Currently, to be able to create a new project using the SnapLogic metadata snaps, having “SnapLogic Read” > “SnapLogic Create” is a definite requirement as the “SnapLogic Read” snap is the one responsible for passing metadata related information (org names, users, acls, etc.,) to the downstream “SnapLogic Create” snap. This rule applies for both creating new projects within (or) across orgs to which you have access to. So, in your case, following the “Router” snap (output 0), you would need to add the “SnapLogic Read” snap followed by the “SnapLogic Create” snap.

Hope this helps.

[psadasivam]

@sriram thanks. It worked 🙂