Free cookie consent management tool by TermsFeed a!queryEntity_22r2() Function
a!queryEntity_22r2() Function

This page contains information related to an old version of the a!queryEntity() Function.

To take advantage of the latest features and improvements, we always recommend you use the latest version whenever possible. See the latest version's page for information about what's been changed.


a!queryEntity_22r2( entity, query, fetchTotalCount )

Executes a query on a given data store entity and returns the result.

See also: Data Store Entity, Query Data Type, a!query()

Tip:  You can use the Query Editor to quickly create and modify queries created with the a!queryEntity() function.


Keyword Type Description


Data Store Entity

The Data Store Entity to query.



The query definition of the report including grouping, aggregation, filtering, paging, and sorting configurations, created with a!query().



If set to false, avoids running the query that retrieves the total number of rows in the totalCount parameter of the resulting datasubset. In cases where you don't need the total count, skipping this query can improve the performance of a!queryEntity(). Default: false.



Usage considerations

Using a!queryEntity

  • The DataSubset returned by this function is used to generate report grids or graphs based on the data in a data store entity. If you have a record type that reference a database, consider using a!queryRecordType() instead to easily reference the record type, or using a records-powered chart or a records-powered grid.

  • If called multiple times in the same expression with the same parameters, only one query is made to the data store when the expression is evaluated and the result is reused for each identical call. This caching only applies within a single expression evaluation. Return values are not cached in separate expressions, or in separate evaluations of the same expression.

  • This function allows a Query object with an array of SortInfo data type.

Using the entity and query parameters

  • The entity value should be given as a constant of type Data Store Entity. The query value must be entered using the a!query() system function.

  • The logicalExpression|filter|search field of the query object can only be set to a LogicalExpression or a QueryFilter type. Search types are not supported.

  • The expression will fail to evaluate and an error will occur if the entity reference is not provided, invalid, or null, the user does not have permission to view the entity, the query value is not provided, invalid, incomplete, or an inconsistent query object.

Using the fetchTotalCount parameter

If fetchTotalCount is set to false and the batchSize parameter in a!pagingInfo is set to -1, the totalCount parameter is populated with the number of rows after the filters are applied. This is because all of the data is already being retrieved, so the value of totalCount is already known without an additional query.

See the following table for more information:

Batch Size Fetch Total Count Scenario Description Value of totalCount
-1 Any value The user wants to get all the rows. We know the total size and return it to the user. Total number of rows after filters are applied
0 or positive true The user only wants a subset of rows, but also wants to know the total number of rows after filters are applied. We run an extra query to get the total size. Total number of rows after filters are applied
0 or positive false The user only wants a subset of rows, and didn't ask for the total number of rows after filters are applied. We don't know the total size. -1


See Query Recipes for examples of queries.

Feature compatibility

The table below lists this function's compatibility with various features in Appian.
Feature Compatibility Note
Portals Partially compatible

Can be used with Appian Portals if it is connected using an integration and web API.

Offline Mobile Partially compatible

Can be used with offline mobile if it is loaded at the top of the form.

Sync-Time Custom Record Fields Incompatible
Real-Time Custom Record Fields Incompatible

Custom record fields that evaluate in real time must be configured using one or more Custom Field functions.

Process Reports Incompatible

Cannot be used to configure a process report.

Process Events Incompatible

Cannot be used to configure a process event node, such as a start event or timer event.

a!queryEntity_22r2() Function