Udostępnij za pośrednictwem


Conventions

For the latest version of Commerce Server 2007 Help, see the Microsoft Web site.

This section explains the table entries used to describe the logical profiles schema.

Property Name

This column indicates the name of the property, which you will use in your code or to export into the Data Warehouse.

Warning

Do not use Commerce Server property names that are the same as SQL Server data types. If you do, Commerce Server will not be able to access those properties.

Data Type

This column indicates the data type of the property. For pre-defined profiles, a logical property is mapped to a physical property of the same name, prefixed with the first letter of the data type and an underscore (for example, the logical address_id, a GUID data type, is mapped to the physical g_address_id).

Note

Commerce Server uses braces ("{" and "}") to surround GUID data types.

Required (Req)

This column indicates whether the property is required.

Exported (Exp)

True (1) indicates the property is exported into the Data Warehouse by the Commerce Server 2007 User Import DTS Task. The DTS task extends the Data Warehouse schema to accommodate any new properties. This property is set in the IsExported attribute of the Property element of the XML representation. If IsExported is set to True (1) for at least one property of the profile definition, then the date_last_changed property must be defined on the profile definition.

Group

A group is a collection of related profile properties. For example, a group named GeneralInfo could be a group containing Name, Address, and Phone properties. Group names must be unique to the profile. Property names, even across different groups, must also be unique. Profile properties are accessed either by their names or in combination with their group name in the format Group.Property (for example, GeneralInfo.address_line1).

Display Name/Description

This column gives additional information about the property.

See Also

Other Resources

Profiles Schema Performance Considerations

Profiles Schema