Personalization Key Guidelines and Limitations

Understand the limitations when configuring MBOs that contain personalization keys.

Maximum length – the value of personalization keys are BASE64 encoded. After encoding, the sum of the length of the personalization key values cannot exceed 16*4000, or a synchronization exception occurs during synchronization.
Personalization keys mapped to parameters and arguments – if a personalization key is nullable and does not have a default value, and is mapped to an MBO sync parameter, load argument, or operation's argument, the default value for that sync parameter, load argument, or operation's argument can be modified, otherwise the default value is empty and read-only.
Mapping a personalization key to operation/synchronization parameter/load argument – if a personalization key is mapped to either an operation argument, load argument, or synchronization parameter, the Properties view default value selection is disabled and the default value is removed.
Setting the personalization key in the device application – the priority with regard to the device application user setting the personalization key value is:
1. The user sets the personalization key value. If the personalization key equals NULL,
2. Use the personalization key default value. If the personalization key default value equals NULL,
3. Use the parameter default value.
In cases where the personalization key is not nullable:
1. the default value for the parameter is never to be used and the default value for the synchronization/operation parameter is read-only.
2. The actual synchronization/operation parameter is not visible from the device application. The device application user cannot overwrite the value with any arbitrary value.
3. Updating the personalization key value results in an update of the original subscription, and not the creation of a second subscription.