To further clarify (from my testing), PATH_INFO is not required in the Parameters option of the Pipeline but still must be accessed via snaps using the “_” prefix. (i.e. “_PATH_INFO”)
can you post the screenshot what you are observing?
_PATH_INFO should be available throughout the pipeline.
What I did was POST to my Triggered Task URL
https://elastic.snaplogic.com:443/api/1/rest/slsched/feed/org/myproject/path/exampleData/3
I wanted to catch the key value pair of exampleData: 3 so I placed it on the pipeline parameter as exampleData
and then I used the mapper to catch and map it to my exampleData field (for my json).
the output of the PATH_INFO is correct which is “exampleData/3”.
or “examplePath”: “exampleData/3”
but if what I wanted to get was the “exampleData”: “3”. is this possible with semantic URL?
Thank you for responding.
Yes certainly.
do split to get those into array.
_PATH_INFO.split('/')
Then use the .map function to form a JSON object with key value pair.
Getting "error_code": 1207 while validating before loading Redshift database | SnapLogic - Integration Nation - 16757
