Hi Randy,

We won't be going back to the old data structure I'm afraid.

These changes were all part of the performance improvements in V4.0, as you can see, even with this small example, the new data structure is far more efficient.

Drop me an email on why you needed the XML and I'll see if we can find a better way for you to get what you need, accessing the XML directly doesn't seem like a good solution.

Nick

Randy, why are you even trying to parse our internal data structure? In another forthcoming version you won't be able to access any Xml.

ITransformProcess.Initialise takes as one argument an TransactionIterator.

You need to use that and not the underlying data structure. 

Thanks

Please also note that the TransactionIterator (and close cousin TransactionSelector) are the only means we use to iterate and transform data.

I’m looking for a way to look at the data INSIDE of an individual Transaction object.

The TransactionIterator appears to only iterator OVER the Transaction objects.

Additionally, the Transaction object itself appears to only allow querying of individual fields.  Is it possible to pull data from a Transaction object without knowing the fieldnames in advance?  In the first iteration of the RAPIDWebSync I used Transaction.Definition to get a collection of TransformRecordField objects.  Is that functionality safe to keep using?

Randy, correct the TransactionIterator does only iterate over Transaction objects.

Yes, the Transaction.Definition is still safe to use; we won't ever break this functionality. 

You may notice BulkGetValue in v4, but you won't be able to use this since it requires a call to a parent object (TransactionFactory) prior to the creation of the TransactionIterator (which is too late for you).

You also have Transaction.Definition.FieldIds() which will return a list of the field ids (and is supremely quick since it returns the index cache).

I hope this helps.