You can create aggregated record queries with URL query parameters or with Presentation API methods.

An aggregated record request is similar to an ordinary record request with these exceptions:

You can use the As parameter to specify a sort that determines the order of the representative records. You can specify one or more sort keys with the As parameter. A sort key is a dimension or property name enabled for sorting on the data set. Optionally, each sort key can specify a sort order of 0 (ascending sort, the default) or 1 (descending sort). The As parameter is especially useful if you want to use the record boost and bury feature with aggregated records.

Similar to an ordinary record, An (instead of N) is the user’s navigation state. Only records that satisfy this navigation state are included in the aggregated record. In addition, the Au parameter must be used to specify the aggregated record rollup key.

The following are two examples of queries using the An parameter:



For the API, the examples below show how the UrlGen class constructs the URL query string. Note the following in the examples:

The AggrERec class calls can retrieve attributes of aggregated records.

After you retrieve an aggregated record, you can use the following AggrERec class calls:

The following code snippets illustrate these calls.

A record in an aggregated record can be displayed like any other Oracle Commerce record.

You display the Oracle Commerce records (ERec objects) in an aggregated record with the same procedures described in Chapter 5 ("Working with Oracle Commerce Records").

In the following examples, a list of aggregated records is retrieved from the Navigation object and the properties of each representative record are displayed.

Copyright © Legal Notices