DSXchange

HI

When data is null in my xml file I am getting following weird data www.w3.org/2001/....... data

XSD : <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">

how to avoid this .

</AssigneesDetails>

ASSIGNEE_TYPE_CODE [xmlns:xsi="http:/XMLSchema-instance" xsi:nil="true"/>

Moderator : I already paid for premium membership and send email but still my profile not updated

<puff of smoke> Moderator here! Two points:

1) There is a specific forum for that particular account issue.

2) We're more like Janitors that clean up posts. Account issues need to be addressed with the site owner and there are stickied posts at the top of the major forums that detail this. (the site owner bit, not so much the janitorial bit)

Hi

Please share your feedback on above issue

thks

If someone had any to share, they would. Patience.

Using xsi:nil is the "deeply specific" way to declare that a particular xml element is a "null" value. One of the reasons it was put into the standard is that there is no real way to tell if <element></element> means "blank"?...or does it mean NULL?

The Hierarchical Stage is heavily controlled by the xml schema definition (xsd)....so....it is able to do the "full" nullability specification.

Consequently...

1. xsi nill means "null". The consumer of your xml should at this time be perfectly capable of handing this standard method of specifying null.

2. I haven't tested this in a long time, but as I recall, the composer step will not put in "nil" unless you "validate" in that Step. Shut off validation and that may make it go away.

3. A lot of sites want "no element at all".........there is an option of whether you want to render null columns as elements.

Ernie