User Guide

Advanced topics in data integration 307
• The optional msg attribute contains a message string that describes the problem that occurred
when attempting the operation
• Zero, one, or more field child nodes give field-level specific information. Each field node,
at a minimum, should have a
name attribute that contains the field name, and a msg attribute
that gives the field-level message. It can also optionally contain a
curValue attribute that holds
the most current value for that field in that row on the server.
Update nodes contain information about records that have been modified since the client was last
updated. Update nodes should have
field child nodes that list the fields that are necessary to
uniquely identify the record that was deleted and that describe fields that were modified. Each
field node should have the following attributes:
• The name attribute holds the name of the field
• The oldValue attribute holds the old value of the field before it was modified. This attribute is
required only when the key attribute is included and set to
true.
• The newValue attribute holds the new value that the field should be given. This attribute
should not be included if the field was not modified (that is, the field has been included in the
list only because it is a key field).
• The key attribute holds a Boolean true or false value that determines whether this field can
be used as a key to locate the corresponding record on the client. This attribute should be
included and set to
true for all key fields. It is optional for all others.
Delete nodes contain information about records that have been deleted since the client was
updated. Delete nodes should have
field child nodes that list the fields that are necessary to
uniquely identify the record that was deleted. Each
field node must have a name attribute, an
oldValue attribute, and a key attribute whose value is set to true.
Insert nodes contain information about records that have been added since the client was
updated. Insert nodes should have
field child nodes that describe the field values that were set
when the record was added. Each
field node must have a name attribute and a newValue
attribute.
Lazy decoding in the WebServiceConnector component
When the WebServiceConnector component receives multiple records of data from a web service,
it translates them into an ActionScript array so they are accessible within your application.
Translating multiple records of data from XML/SOAP into ActionScript native data can be a
time-consuming process; large data sets become large arrays, and can take seconds or tens of
seconds.
To improve performance, the WebServiceConnector component supports a feature called lazy
decoding, which defers this translation. With lazy decoding, result values that are arrays are not
immediately translated from XML to ActionScript. Instead, the result value passed to the user is a
special object that acts similarly to an array and translates the XML data only when it is requested.
The effect of this feature is to improve the perceived performance of web services by spreading the
workload over a longer period of time.