Content conversion (help required)

[Former Member]

Hi,

i have a file structure as follows....

01xxxxxxxx -

---

>(will occur ony once in file)

02xxxxxxxx

03xxxxxxxx

03-----

03-----

04xxxxxxxx

02....

03....

03....

04.....

05..... -

---

>(will occur ony once in file)

i defined my data type as

DT_INPUT

|__details

|__header occ:1

|__bheader occ: unbounded

|__body occ: unbounded

|__btrailer occ: unbounded

|__trailer occ: 1

can you help me how to go about with the content conversion for this?

when i gave the recordset as details

and the recordset structure as

header,1,bheader,,body,,btrailer,*,trailer,1

it works well when i give data as

01------

02-----

03-----

03-----

03-----

04-----

05-------

but once i start repeating the

02-----

03-----

03-----

03-----

04-----

structure, it throws an error....

Sender Adapter v1508 for Party '', Service 'BS_WWW':

Configured at 19:06:34 2005-05-13

Last message processing started 19:07:27 2005-05-13, Error: Conversion of complete file content of 'test.txt' to XML format failed around position 0 with java.lang.Exception: ERROR consistency check in recordset structure validation (line no. 6: missing structure(s) before type 'bheader'

last retry interval started 19:07:27 2005-05-13

length 10,000 secs

[Former Member]

your structure definition I think it what is biting you. If you want 2,3,4 to repeat under 1, they must be nested under 1, not on the same level.

1 (1)

-lineholder (unbounded)

--2 (unbounded)

--3 (unbounded)

--4 (unbounded)

5 (1)

is really what you are going for - so "lineholder" can repeat.

I have not set up content conversion on that type of structure yet. I realize in real life, the scenario isn't that complex, but content conversion, and all the examples, don't go into nesting like you're talking about - only children, and different types of children... let me read & see if I can find a similar example.

[Former Member]

I tried to recreate your problem, but without success... I'm on SP11 - not sure which you are at.

Idea - if your DT definition has all elements (1,2,3,4,5) on the same level, keep your cardinality the way it is, you should be able to read in the data you need, even with repeating sections 2-4. Inside your GUI mapping, add context changes to re-organize your structure the way you intend it, and then you should be able to map the way you need to.

[Shabarish_Nair]

Hi Amanda,

guess what !!! there is something else we can actually do here...

we need to modify the DT as follows....

DT_INPUT

|___header occ:1

|___bheader occ: unbounded

|___body occ: unbounded

|___btrailer occ: unbounded

|___trailer occ: 1

and during content conversion, specify as follows...

the recordset as details

and the recordset structure as

header,1,bheader,,body,,btrailer,,<b>trailer,</b>

and then we need to add

<b>ignoreRecordsetName = true.</b>

this happens to solve the problem.....

Regards,

ShabZ

Message was edited by: Shabarish Vijaykumar