MACROMEDIA FLASH 8-FLASH, Use Manual

Page: 431 / 678

Advanced topics in data integration 431
However, in some cases, you might find that the values you’re sending to your external data
source are not formatted correctly. This can occur when you don’t use a connector to retrieve
your data or you want to change the format of the data to be sent to an external data source.
In this case, you can control the formatting by adding properties to the resolver component’s
schema. For instance, if you have a Boolean field called Billable in your DataSet component,
its value can be formatted in an update packet as
true
or
false
. If you want it formatted as
yes
or
no
, you can create a new component property called
Billable
within the Schema tab
for your resolver. Using the schema settings, you can set the data type as Boolean, the encoder
as Boolean, and the encoder options as
yes
or
no
. The encoder is applied when the resolver
creates the update packet, and the value for the billable field is represented as
yes
or
no
.
For more information, see “Adding a component property to a schema” on page 398 .
Advanced topics in data integration
This section discusses advanced topics, such as refinements you make to schema settings
and information for developers who need to write server-side code to interact with Flash
data applications.
Schema item settings
This section contains details about schema item settings and how you edit them. To help you
determine whether or not you need to look at schema item settings, see
“When to edit schema
item settings” on page 443 .
The schema of a component shows what properties and fields are available for data binding.
For each property or field, there are settings that control validation, formatting, type
conversion, and other features that affect how data binding and the data management
components handle the data of a field. The Schema Attributes pane, the bottom pane of the
Schema tab, presents these settings, which you can view and edit. The following list describes
the five categories of settings, according to the features they control:
Basic settings Every field or property has these basic schema settings. In many cases, these
are the only settings you need to bind to a field:
■
Name: Every field needs a name.