I am using a datawindow for generation of an XML file where have a
block of data for the address information.
Looks like this when exported

<Address>
<Line>bla bla bla</Line>
<Line>bla bla bla</Line>
<Line/>
<Line/>
</Address>

In this case the employee only have 2 address lines and the export
allows for 4.
The recieving system treats the 2 empty lines as errors and i would
therefore like them not to
be generated when exporting this data.
Is there anyway i can avoid this from inside PB using a export XML
template from a datawindow?
Or do i have to run through my XML file after generation using PBDOM
and removing empte child
elements.

All help appreciated

How is somebody that is going to use this XML distiguish between the
various lines of the address? AFAIK, child elements should have
unique names (e.g., line1, line2, line3, etc.)

If you've got a client that is trying to import the file and is having
problems, it may be due to the non-uniqueness of the child element
names rather than because some are null.

On Thu, 22 May 2008 02:06:30 -0700 (PDT), Steen Christiansen
<Stc.nordrupby20@gmail.com> wrote:

>I am using a datawindow for generation of an XML file where have a
>block of data for the address information.
>Looks like this when exported
>
><Address>
><Line>bla bla bla</Line>
><Line>bla bla bla</Line>
><Line/>
><Line/>
></Address>
>
>In this case the employee only have 2 address lines and the export
>allows for 4.
>The recieving system treats the 2 empty lines as errors and i would
>therefore like them not to
>be generated when exporting this data.
>Is there anyway i can avoid this from inside PB using a export XML
>template from a datawindow?
>Or do i have to run through my XML file after generation using PBDOM
>and removing empte child
>elements.
>
>All help appreciated