KB-1945 Unexpected sort ordering when using a!queryEntity

Maggie Deppe-Walker — Tue, 08 Nov 2022 23:43:09 GMT

Current Revision posted to Appian Knowledge Base by Maggie Deppe-Walker on 11/8/2022 11:43:09 PM

This issue has been resolved in a new Appian version. Please upgrade to the latest version of Appian.

Symptoms

When using a!queryEntity without a sortInfo parameter specified, a seemingly arbitrary sort order is applied to the data. Specifically, the following behaviors are seen:

If no a!querySelection is present, the result set is sorted on the last column of the CDT representing the table.
If a a!querySelection is present, the result set is sorted on the first a!queryColumn value specified in the definition.

As a result of this, performance issues may be observed if the query returns a lot of data or is sorting by a text column.

Cause

This issue has been resolved via AN-128642 in Appian 22.3 GA.

Action

Upgrade to Appian 22.3.

Workaround

Sorting by the primary key is typically the most efficient sort order. Thus, a sort parameter referencing the primary key should be set for the pagingInfo used by the queryEntity.

Affected Versions

This article applies to Appian 22.2 and earlier.

Last Reviewed: November 2022

Tags: known issues, application server, fixed issues, queryEntity

KB-1945 Unexpected sort ordering when using a!queryEntity

Maggie Deppe-Walker — Tue, 08 Nov 2022 23:42:33 GMT

Revision 4 posted to Appian Knowledge Base by Maggie Deppe-Walker on 11/8/2022 11:42:33 PM

This issue has been resolved in a new Appian version. Please upgrade to the latest version of Appian.

Symptoms

When using a!queryEntity without a sortInfo parameter specified, a seemingly arbitrary sort order is applied to the data. Specifically, the following behaviors are seen:

If no a!querySelection is present, the result set is sorted on the last column of the CDT representing the table.
If a a!querySelection is present, the result set is sorted on the first a!queryColumn value specified in the definition.

As a result of this, performance issues may be observed if the query returns a lot of data or is sorting by a text column.

Cause

This issue has been resolved via AN-128642 in Appian 22.3 GA.

Action

Upgrade to Appian 22.3.

Workaround

Sorting by the primary key is typically the most efficient sort order. Thus, a sort parameter referencing the primary key should be set for the pagingInfo used by the queryEntity.

Affected Versions

This article applies to Appian 22.2 and earlier.

Last Reviewed: November 2022

Tags: application server, queryEntity

[DRAFT SP 7999] KB-1945 Unexpected sort ordering when using a!queryEntity

Daniel DeVeau — Mon, 07 Nov 2022 14:24:24 GMT

Revision 3 posted to Appian Knowledge Base by Daniel DeVeau on 11/7/2022 2:24:24 PM

This issue has been resolved in a new Appian version. Please upgrade to the latest version of Appian.

Symptoms

When using a!queryEntity without a sortInfo parameter specified, a seemingly arbitrary sort order is applied to the data. Specifically, the following behaviors are seen:

If no a!querySelection is present, the result set is sorted on the last column of the CDT representing the table.
If a a!querySelection is present, the result set is sorted on the first a!queryColumn value specified in the definition.

As a result of this, performance issues may be observed if the query returns a lot of data or is sorting by a text column.

Cause

This issue has been resolved via AN-128642 in Appian 22.3 GA.

Action

Upgrade to Appian 22.3.

Workaround

Sorting by the primary key is typically the most efficient sort order. Thus, a sort parameter referencing the primary key should be set for the pagingInfo used by the queryEntity.

Affected Versions

This article applies to Appian 22.2 and earlier.

Last Reviewed: November 2022

Tags: application server, queryEntity

[DRAFT SP 7999] KB-1945 Unexpected sort ordering when using a!queryEntity

Daniel DeVeau — Mon, 07 Nov 2022 14:23:32 GMT

Revision 2 posted to Appian Knowledge Base by Daniel DeVeau on 11/7/2022 2:23:32 PM

This issue has been resolved in a new Appian version. Please upgrade to the latest version of Appian.

Symptoms

When using a!queryEntity without a sortInfo parameter specified, a seemingly arbitrary sort order is applied to the data. Specifically, the following behaviors are seen:

If no a!querySelection is present, the result set is sorted on the last column of the CDT representing the table.
If a a!querySelection is present, the result set is sorted on the first a!queryColumn value specified in the definition.

As a result of this, performance issues may be observed if the query returns a lot of data or is sorting by a text column.

Cause

This issue has been resolved via AN-128642 in Appian 22.3 GA.

Action

Upgrade to Appian 22.3.

Workaround

Sorting by the primary key is typically the most efficient sort order. Thus, a sort parameter referencing the primary key should be set for the pagingInfo used by the queryEntity.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: November 2022

Tags: application server, queryEntity

[DRAFT SP 7999] KB-1945 Unexpected sort ordering when using a!queryEntity

Maggie Deppe-Walker — Mon, 07 Nov 2022 00:43:11 GMT

Revision 1 posted to Appian Knowledge Base by Maggie Deppe-Walker on 11/7/2022 12:43:11 AM

Symptoms

When using a!queryEntity without a sortInfo parameter specified, a seemingly arbitrary sort order is applied to the data. Specifically, the following behaviors are seen:

If no a!querySelection is present, the result set is sorted on the last column of the CDT representing the table.
If a a!querySelection is present, the result set is sorted on the first a!queryColumn value specified in the definition.

As a result of this, performance issues may be observed if the query returns a lot of data or is sorting by a text column.

Cause

This issue has been reported to the Appian Product Team. The reference number for this issue is AN-128642.

Action

Sorting by the primary key is typically the most efficient sort order. Thus, a sort parameter referencing the primary key should be set for the pagingInfo used by the queryEntity.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: May 2019