ProjectedFields Element (View)

Article
10/20/2016

Applies to: SharePoint Foundation 2010

Specifies the fields in joined lists that can be included in the view when one or more other lists have been joined in a query.

<ProjectedFields>   
  <Field ... />  
  <Field ... />
</ProjectedFields>

Attributes

None

Child Elements

Field

Note

There is a maximum number of Field child elements. It is defined as the difference between the maximum number of allowed fields in the list and the number of fields that are already in the list.

Parent Elements

View

Occurrences

Note

The View element cannot have a ProjectedFields element unless it has a Joins element that has at least one Join child element. However, a ProjectedFields element that forms the value of a SPQuery.ProjectedFields property, and therefore, is not a child of a View element, can be used to support an implicit join without a Joins element. We do not recommend working without a Joins element. You will maximize your solution’s chances of being compatible with future releases of Microsoft SharePoint Foundation by always using an explicit Join element. For more information about implicit joins with ProjectedFields elements, see List Joins and Projections.

Minimum: 0

Maximum: 1

Remarks

If a field from a joined list is not represented in ProjectedFields, it cannot be included in the ViewFields element.

Example

The following example shows how to add another field to the results that are returned by the query. The value of the List attribute is an alias to the foreign list. The alias is defined in a Join Element (View). The ShowField attribute must be set to the internal name of the foreign field.

The Type attribute does not indicate the data type of the field as it usually does in a Field element. When a Field element is a child of a ProjectedFields element, Type simply indicates whether the Join element (in the Joins element on which the ProjectedFields element depends) is based on an existing lookup relation between the lists. As of SharePoint Foundation 2010, all joins must be based on an existing lookup relation, so Type always has the value "Lookup". The actual data type of the field is not indicated when it is a child of the ProjectedFields element. However, the field’s data type does matter because only the following types of fields can be included in a ProjectedFields element:

Calculated (treated as plain text)
ContentTypeId
Counter
Currency
DateTime
Guid
Integer
Note (one-line only)
Number
Text

<ProjectedFields>
  <Field
    Name=’CustomerCity’
    Type=’Lookup’
    List=’customerCities’
    ShowField=’Title’ />
</ProjectedFields>

For an example of a ProjectedFields element whose child Field element has a FieldRef attribute instead of a List attribute, see List Joins and Projections.

Share via