CSV Node Input Parameters

General
1

Hi,

I have a question regarding the standard "csv node".

The node offers to input data in msg.columns. What about other parameters, e.g. the separator, the number of lines to skip, etc.? These are useful parameters and could make the node's usage more flexible. The node itself is able to use different separators, but I don't see how to set them in a message.

Are those parameters not available or not documented?

2

These options are not dynamically settable at runtime.

3

Well, I expected this. However, it would be great to implement some more flexibility.

4

Not sure how that would work - if it changed every message what would you expect the output to be ?

5

I have the situation, that I receive CSV files from different sources. Their content is logically similar, but the order of the columns and formats are different. An example could be lists of authorizations in different systems, where every system returns a slightly different format, but the data is logically similar.

Some files are separated by semicolon, others by comma, pipe, or whatever. The processing logic should handle that.

At the moment I have a switch node, that switches to different csv nodes, just to handle the different separators. Not a very nice solution (but works).

So, why not having such information optionally in a message. Same with the other options as these also could vary.

6

I think the solution you have is logically the cleanest... If they come from different sources then handle that first - route them to the individual "handlers" that are easy to visually see and debug - then recombine when normalised.

7

Yep. However, some more flexibility would be great.

Like the filein node, that had been enhanced in v3.

Anyway. thanks all for your comments.

8

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.