This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
I have a file called “File With Spaces.csv” and am trying to create a GLOB pattern to match it in a Director Browser.
What should work does not work and what does work is not optimal in my opinion.
Simply setting the File Filter to the value: File Wi...
We often send an email in our pipelines have certain errors, and we also have a lot of Tasks that drive the same pipeline(s) but with different params.
So it would be very helpful if when could send the name of the Task that started a failed pipeline...
We are trying to integrate with an external app’s WebHook event system, but they currently do not allow for the setting of HTTP headers to include in the POST request. This makes it impossible for us to use a triggered Task’s URL directly for the web...
When writing expression it would be useful to know, in some cases, whether or not the context is in validation mode or not.
A specific example is when paging in a REST Get Snap: when in validation mode you will get errors about “slot allocation” when...
Hi Rakesh,
“File With Spaces.csv” does not work either, but using “File%20With%20Spaces.csv” does the trick.
File???With???Spaces.csv also does the trick (as quoted expression or not), so it is clear now that it has to do with the encoding from the s...
Actually it looks like using %20 works for the space character matching.
Perhaps it has to do with the fact that I am browsing an SFTP directory?
Seems reasonable but kind of violates the Principal of Least Surprise.
TK
Assuming that you have a response from the api that has a field with the value as a CSV string, you can map that field to $[‘content’] in a Mapper, then use a Document to Binary Snap to convert to “binary” and then use a CSV Parser to create the JSON...
Other possible solutions:
maybe a json mediaType can be requested from the web service (e.g., Accept or Content-Type headers)
the html might be processed as XML:
map the “entity” field to $[‘content’] and then run through Doc->Bin Snap then XML Par...
Hi @wogen,
You could possibly use the Pipeline Execute Snap with a collection of sub-pipelines that perform the formatting/writing.
This way the PipeExec would act as the “router” and you can use a naming convention for the sub-pipelines that include...