Thank you for providing a detailed outline. I’ve been away implementing this and looking at the right expressions to use to split/concatenate the data. I’ve managed to put the pipeline together however the Mapper snap isn’t returning any data based on the expression provided:
This is a copy of the JSON message before it goes into the Mapper. There is currently no data in the csv file hence the blank message on input0
[
{
“input0”: [
],
"input1": [
{
"A": "X",
"B": "X",
"C": "60",
"D": null,
"E": "X",
"F": "",
"G": "X",
"H": "X",
"I": "1320159",
"J": 1430047,
"K": "X",
"L": "X",
"M": "X",
"N": "X",
"O": false
}
]
}
]
If input0 contains the new data in your pipeline, you should write the following expression:
$input1.concat($input0)
This is working fine for me. Result:
[
{
"A":"X",
"B":"X",
"C":"60",
"D":null,
"E":"X",
"F":"",
"G":"X",
"H":"X",
"I":"1320159",
"J":1430047,
"K":"X",
"L":"X",
"M":"X",
"N":"X",
"O":false
}
]
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.
@sriram thanks. It worked 🙂
