The totalCount is 1 because the data store entity's primary key is set to PERSONID. The underlying view produces two rows for "John" due to the one-to-many relationship. However, when Appian's a!queryEntity function executes, it de-duplicates the results based on the designated primary key. Since both rows for "John" share the same PERSONID (1), they are counted as a single unique item, resulting in a totalCount of 1.

By default, a!queryEntity executes a second database query (SELECT COUNT(...)) to calculate the totalCount. This query uses the same filters as the main data query but ignores the paging configuration to get the total number of matching (and de-duplicated) records.

B. result totalCount is 3: This is incorrect because the query applies a filter name = "John", which limits the results to only that person.

D. Appian makes one more query to the database(other than the actual query to fetch the data) to get the totalCount based on the applied filters and paging info.: This is incorrect because the totalCount query is intentionally independent of the pagingInfo to reflect the total number of records available.

1. Appian Documentation

a!query() function: The fetchTotalCount parameter

which defaults to true

is described as: "When true

the query will execute a second query to retrieve the total number of results that match the filters." This supports answer A. (Appian 23.4 Documentation

"Functions Page"

a!query section).

2. Appian Documentation

Data Store Entity: When creating a data store entity from a database view that represents a one-to-many relationship

setting the primary key to the ID from the "one" side is a standard practice. The documentation states: "When you query from the view

Appian will only return one row for each distinct primary key value." This de-duplication applies to both the data returned and the totalCount calculation

supporting answer C. (Appian 23.4 Documentation

"Data Stores" page

"Create a Data Store Entity from a Database View" section).

3. Appian Documentation

a!queryEntity() function: The description of the totalCount field in the returned DataSubset specifies it is "the total number of items in the data store entity that match the filtering and search criteria

before paging is applied." This confirms that paging info is not used for the count

making answer D incorrect. (Appian 23.4 Documentation

"Functions Page"

a!queryEntity section).