Client parameters and personalization keys cannot include large object (BigString or
BigBinary) types, and cannot have a structure (or list of structures) type that contains
large object fields.
If an operation argument has a:
- Large object type – map a client parameter or personalization key
into the argument, and use a compatible type (String or Binary) for the client
parameter/personalization key.
- Structure (or list of structures) type that contains large object
fields – map a client parameter or personalization key into the argument if the
type of the client parameter/personalization key is a structure (or list) with
compatible fields.
For example, if the operation argument structure is:
MYSTRUCT
mystr[STRING(10)]
mybigbin[BIGBINARY]
this is a compatible structure type:
CP_MYSTRUCT
mystr[STRING(10)]
mybigbin[BINARY(32767)]
To easily create a client parameter or personalization key that matches
the type of the argument and automatically add a mapping from the argument to the new
client parameter/personalization key, drag and drop an argument into the Personalization
Keys or Client Parameters folder of the Input Mapping figure. When the argument is a
structure containing large object fields, and you drag and drop it on the
Personalization Keys or Client Parameters folder, a new compatible structure type is
created:
- For client parameters – a new client parameter is added with the
compatible type, and the mapping added.
- For personalization keys – the New Personalization Key wizard
is invoked, with the initial type set to the new compatible structure type.