DSXchange

Haven't tried this, but the closest I think you might get is to look at the various XML Stages --- xml Input, xmlOutput and the xmlTransformer. Each of these has the option to include XSLT --- and then adjust output "however you want". It requires that you have extensive knowledge of XSLT ...

:) same concept in reverse, assuming that the body is also a complex xml doc. Put one big column on the output link.....like "mySOAPresponse" longvarchar and put a single "/" (slash) in the Description property. No other cols. Then use the same "user dfined message" pul...

Look at the special property in the input link for "user defined" message. Have that point to the single large varchar column that you built upstream with the whole payload. ...and the best thing to do is to first test this by: 1. run your service via SOAPui or other tool. 2. copy a workin...

More difficult. For this you need to build thr entire soap payload yourself... the web services transformer isnt able to build a complex multi node independenly repeating xml payload. It can be built upstream via multiple xml output stages or via the hierarchical stage. Both require testing and lear...

Great discussion. It is worth noting also that a lot of sites will have a separate instance of Information Server for IGC and governance activities. This is primarily because the upgrade effort to get the "latest GUI", etc. is often not as exhaustive as upgrading/testing all of your DataSt...

Nice solution!

Not sure at this point what is on the agenda.

Ernie

Looks like a classic poorly designed xml. Better would have been to have an actual element called "<StartDate>" and another called <EndDate> and populate them appropriately. For something like this, just build the little xml chunk in a transformer and include it in the Description property...

They work nicely, and provide an easy way to extend the repository, albeit not as elegant as OpenIGC.

Ernie

Based on this kind of straight path hierarchy, I would use xml output and skip the hierarchical stage. You dont need it. It only makes sense when you have parallel siblings to produce for a given order, such as maybe multiple purchasers. There may be other variables in your requirement but so far, x...

Perfect for OpenIGC. See the toc at www.dsrealtime.com

Not sure if or how the hierarchical stage decides. In the xmloutput stage you have a choice. Either way, it doesnt matter. Both are the same. You might want to check to see if validation is on.

Ernie

Team Foundation Server ...is that another Source Code management system? I haven't ever heard of that one, but perhaps it is another Eclipse based offering that "perhaps" IDA could connect to? I am not an IDA expert and don't follow it closely, so maybe something was done formally, but if ...

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 Sta...

This is a good discussion.... XML, as a standard ,supports two similar methods for indicating an "empty" element. <element/> and <element></element> Both are entirely equivalent --- the mean the same thing. Some have argued in the past that one is more readable than the other...and certain...