Forum Discussion

mohamadelmardin's avatar
mohamadelmardin
New Contributor III
9 years ago

Creating project using Metadata SnapLogic Create snap

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...
dmiller's avatar
dmiller
Former Employee
5 years ago
Copy LinkReport

@cjhoward18 to the rescue. 🙂
Date.parse("2020-09-01T00:00:00.000").toLocaleDateString({"format":"yyyyMMdd"})

mtran21's avatar
mtran21
New Contributor III
5 years ago
Copy LinkReport

Thanks, will this work with variable?
Date.parse(“$HIRE_DATE”).toLocaleDateString({“format”:“yyyyMMdd”})

  • sriram's avatar
    sriram
    Former Employee
    9 years ago
    Copy LinkReport

    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.