The next table presents the properties of the Aggregate.

Property

Description

Optionality

Default value

Obs.

Name

Text that identifies the aggregate. The scope of the aggregate depends on the scope of the action.

Mandatory

 

Learn more about rules for naming elements.

Description

Free text that describes the aggregate. You can edit the text by directly typing it in the property or in the description editor which opens by clicking

Optional

 

Useful for documentation purposes.

 

The maximum size of this property is 2000 characters.

Timeout in seconds

Defines the maximum time Platform Server waits for this aggregate to be executed, since the database connection was established.

 

This value is defined in seconds.

Optional

 

If there is no value specified in this property, the aggregate time-out corresponds to the Default query timeout parameter specified in the Platform Server Configuration Tool.

Cache in Minutes

Indicates how long the aggregate results remain in cache. However, if the cache is invalidated during this time, they are removed from the cache.

Optional

Empty value; means that the element is never cached.

To improve the runtime performance of your aggregate, you can use cache, to avoid fetching twice the same data from the database. Learn more About Caching Contents.

Max. Records

Maximum number of records that are fetched from the database.

Optional

 

If you don't know exactly the number of records that the List must have, you should specify a number big enough to handle these situations. For example, when you want to get all the rows of a table or delete a set of rows.

 

If a value is not specified, the OutSystems Platform uses the following as Max. Records:

  • In Widgets

StartIndex + LineCount + 1

  • Exporting to Excel

No limit of records

Executed SQL

The last SQL statement used to fetch data from the database.

 

The statement used in runtime is optimized to fetch the necessary number of rows and columns.

 

 

This property is read-only.

 

The SQL statement displayed might be different from the one used in runtime since the latter is optimized to fetch the necessary number of rows and columns.

See Also

Filtering Results | Supported Join Types