cancel
Showing results for 
Search instead for 
Did you mean: 

File content conversion: nodes have multiple occurence and is jumbled

Former Member
0 Kudos

Hi,

Here is one structure used in file content conversion.

Header

Dataline1

Dataline1

Dataline1

Dataline2

Dataline2

Dataline2

Header, Dataline1 and Dataline2 are nodes containing more than one fileds.

We have mentioned 'fieldSeparator', 'EndSeparator' and 'keyFieldValue' for each of the nodes Header, Dataline1 and Dataline2 .

Now the requirement has changed and the source file structure is as given below.

Header

Dataline1

Dataline2

Dataline1

Dataline2

Dataline1

Dataline2

Now with the same communication channel, the content conversion picks up only the first occurence of Dataline1, Dataline2 ie only this much

(Header

Dataline1

Dataline2)

is being picked or read.

The other occurences are lost, even though logically it should pick all of them, since 'keyFieldValue' is specified for each node..

Should I give any extra parameters in the communication channel for file content conversion.? or else what is the best way to proceed

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi John !

Have you checked the recordset structure in the file content conversion parameters?? like "Header,1,Dataline1,,Dataline2, " to specifiy that it should be 1 header structure, N dataline1 and N dataline2 ??

Regards,

Matias.