Issue with Optional Checkbox in XML stream


We have an xml stream something like ..


we have checked the optional check-box for "Test" element and no property is associated with this element.At run time when there are no values for "Test1"(which has property associated),still the "Test" tags are generated.Is there a way by which extra tags are not generated for the elements which are not associated with a property.

**Moderation Team has archived post**

This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.


Keep up to date on this post and subscribe to comments

January 14, 2011 - 12:58pm

The checkbox should work when applied to a child node, but I doubt it is valid for the root node of the stream rule. What's the use case here? Is this stream included from another stream? If it is, then the optional flag on the including node of the parent rule should omit the content as you would expect. If it is not being included by another stream rule, then producing XML stream content that has no root element node doesn't make any sense.

January 15, 2011 - 1:59am

Thanks TANDP for the response,

Yes this stream is included in another stream ,optional flag is selected on the including node of the parent rule .The problem here is, tags for the elements which don't have property associated are generated in the called stream and for the remaining elements in it ,tags are not generated as property is associated to those and there is no value for those properties at run time.

Referring to my previous post,the "Test" element tags are generated(which doesn't have any property associated just a plain element)and although there is no value for "Test1" element on the clipboard.

January 4, 2012 - 12:52pm


We do have a similar kind of issue where the Root node tags are generated by default. Do you have any solution to suppress this tags.


February 16, 2014 - 11:05am

mark the tag as optional, both in the Parse XML rule also in he XML Stream rule. if you don't change in the both rule then it will not work.


there should be XML stream rule with the same name of the parse XML rule.





March 16, 2014 - 5:27am

Hi ,


Once you do the parsing using Apply-Parse xml rule, it will create empty property properly.

But the problem arrives when you store in DB and fetch it again.It will remove all blank property.

And I hope you would be using Data transform to created destination structure.

It will not find those property in Source page(as it will be reopened from DB) and will not create at all for you in Destination page.