We're using the 'LastStatementDate' in Person record, and the initial addition of the information works well. However, any attempts to 'nullify' the existing data fails, and the LastStatementDate refuses to be updated when null values were entered. It only gets updated only when non-null data are entered.
There seems to be no documentation to explain this sort of actions, and I'd like to know whether this sort of behavior is bug or by design.
Pinned topic Now to nullify 'LastStatementDate' in Person record?
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-09-05T06:57:41Z at 2012-09-05T06:57:41Z by SystemAdmin
SystemAdmin 110000D4XK345 Posts
Re: Now to nullify 'LastStatementDate' in Person record?2012-09-05T06:57:41ZThis is the accepted answer. This is the accepted answer.
- SystemAdmin 110000D4XK
The nullFields element is a list of element names used to support the Nullable Fields feature.
It lists those elements in the PersistableObject that must be nulled. It is considered an error if an element of a PersistableObject is listed as a null field in nullFields and at the same time appears in the PersistableObject.
For example, when used with a Person type to null the displayName, alertIndicator, and lastStatementDate fields in an updateParty SOAP message, it would be represented like this:
<party xsi:type="Person" nullFields="displayName alertIndicator lastStatementDate"> ... </party>
Hope it helps,