Value

TRUE or FALSE

If set to TRUE, duplicates of the same record are not returned in the result sets of queries executed on the business component in ForwardOnly mode. Aggregation is done in memory on the set of unique records only. The aggregation is not performed as part of the SQL.

If this user property is set to FALSE or it is not defined on the business component, duplicates of the same record are included in the result sets of queries executed on the business component in ForwardOnly mode. In general, the aggregation is done as part of the SQL, that is, the aggregation is done in the database layer. Aggregation in the database layer is preferred for performance considerations. However, the aggregation is done instead by the Siebel Object Manager after all rows are read from the database if any of the following exceptions apply:

• The Database Aggregation Flag parameter in the Server Datasource named subsystem is FALSE (in server mode), or the parameter DBAggregation parameter is defined and set to FALSE in the application's .cfg file on the Mobile Web client.

  For information on setting application object manager named subsystem parameters, and for information on setting .cfg file parameters on the Mobile Web client, see Siebel System Administration Guide.

• A search specification has clauses that cannot be evaluated by the database, thus requiring evaluation in memory.
• Aggregation in the database fails for some reason.

NOTE:  The Duplicate Elimination user property only determines how aggregation is done. To enable aggregation on a list column or for a multi-value link requires that you first make several settings in Siebel Tools.

For information on configuring a list applet to display totals, see Configuring Siebel eBusiness Applications.

For information on showing totals in a separate applet for a multi-value link, see Configuring Siebel eBusiness Applications.

Usage

This user property allows the developer to configure whether duplicates are included in ForwardOnly queries on the business component. If a query is executed in ForwardOnly mode, the same record may repeat in the result set for one of the following reasons:

• The intersection table has duplicate rows. For example, Start Date is part of the association, and associations with different start dates are logically unique.
• The join is to one or more destination columns that are non-unique, and there are no join constraints or run-time search specifications applied.
• Some cases exist for which the application logic may require denormalizing the relationship and viewing all the associations in the context of the parent record. Even if there are no duplicate associations, the same parent row repeats in the result set as associations to different child records in the intersection table. In this case, it may be preferable to not reject duplicates.

You can inactivate this user property or modify its value. You can create new instances of this user property, but you should not create more than one instance for a business component.

Parent Object Type

Business Component