Summary of Support for Extension Tables and Extension Columns
The following table summarizes support for extension tables and extension columns.
Object | Description |
---|---|
Public data table |
Can be extended by using an extension table and extension columns. |
Private data table |
The following support is available for the private data table:
A private data table is a table with the Type property set to Data (Private). Some interface tables are private, but most are public. |
Intersection table |
The following support is available for an intersection table:
|
LOV Bounded, LOV Type property of a table column |
Read-only for a predefined column in Siebel CRM but is editable for a custom extension column. MLOV (multilingual list of values) is allowed with a custom extension column. |
Predefined one-to-one extension column |
It is recommended that you do not modify or delete a predefined one-to-one extension column. |
Predefined extension column |
Similar to a data column in a base table, you must not modify or delete a predefined extension column that a predefined Siebel application uses. |
Custom extension column |
The following support is available for a custom extension column:
|
Custom extension table |
The following is available for a custom extension table:
|
EIM mapping |
The following support is available for Enterprise Integration Manager (EIM) mapping:
For more information, see Mapping a Custom Table to an Interface Table. |
Custom extension to a dock object |
The Dock Object Mapping Wizard allows you to associate a new table with a predefined or a new custom dock object. This support allows Siebel CRM to synchronize data that resides in the dock object of a Remote user. |