SPMobileBaseFieldControl.PostValue, propriété (Microsoft.SharePoint.MobileControls)

Windows SharePoint Services 3
Gets the value that the field will have after the next postback of the page.

Espace de noms : Microsoft.SharePoint.MobileControls
Assembly : Microsoft.SharePoint (dans microsoft.sharepoint.dll)

public virtual Object PostValue { get; }

Valeur de la propriété

An Object that represents the value that the field will have after the next postback of the page.

The default implementation returns the same value that is in Value and the latter property's default implementation returns the same value as ItemFieldValue.

Override the PostValue getter when the field expects values in a special format. For example, if the field expects percentages, the getter should divide Value by 100.

Remarques à l'attention des héritiers : We recommend that you maintain the following relationship between the ItemFieldValue, Value, and PostValue properties and the TrySaveFieldValue method in your derived classes.
  • ItemFieldValue is the value of the field after the most recent saved change. Unsaved changes, whether made by the user in the UI or by code behind, are not reflected in ItemFieldValue.

  • Value is usually identical to ItemFieldValue immediately after each load of a page or postback, but it can be changed. Typically the change is made through the UI and is not saved until the user takes additional action, such as clicking a Save control. Before the save, Value and ItemFieldValue have different values.

  • PostValue is identical to Value in most cases, but it can be useful when users are entering values for Value that are not in the format that the field expects. Use PostValue to hold the correctly formatted version of the value. For example, if the field holds a percentage that users are entering as whole numbers, but the field requires that the value be a fraction of 1, PostValue could be Value divided by 100.

  • TrySaveFieldValue is called when a change to a field is being saved, usually as part of an iteration trough all the fields of a list item. It writes the value of PostValue to both ItemFieldValue and Value.

For example, suppose the field is Boolean and rendered as a check box. When the page first loads, ItemFieldValue is false and the check box is not checked. This means that Value is also false, and so is PostValue because there is no special formatting for this Boolean field. The user clicks the check box and Value (and PostValue) become true. The user clicks a Save button and ItemFieldValue becomes true. For a second example, suppose the field is a text field in which users enter a percentage as a whole number, but for which values are stored as a fraction of 1. When the page first loads, the ItemFieldValue, is 0.15 and Value is 15. PostValue is 0.15. The user changes the 15 to 40 and Value becomes 40, and PostValue becomes 0.4. The user clicks a Save button and ItemFieldValue becomes 0.4.
Afficher: