Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
4 replies
Subscribers
4 subscribers
Views
5537 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Reports
How to use a!querySelection with a!queryProcessAnalytics
marky
over 8 years ago
Hello:
selecting a column such as "c3" is not working and returning null.
Any idea how to use a selection field for a process task report query?
We need to have 15000+ tasks in the task report, so we need to get a count of the total and use paging to handle this much data.
Thank you,
OriginalPostID-248800
Discussion posts and replies are publicly visible
0
sikhivahans
over 8 years ago
@marky Hi, re querySelection - I believe selection (and aggregation as well) isn't possible in the queryProcessAnalytics as of now and here are the lines from documentation at https://forum.appian.com/suite/help/16.1/System_Functions.html#a!queryProcessAnalytics.28.29: Columns cannot be selected or aggregated via the query parameter but can be configured in the process report.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
sikhivahans
over 8 years ago
@marky In case if count of 15000 is an issue, please let me know.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
vijaykumars282
over 8 years ago
Marky,
Please try to use it in following way :-
a!queryProcessAnalytics(
report: cons!PRT_DOC_PRICING_TASKS_REPORT,
contextProcessModels: cons!PRT_PM_SEND_QUOTE_REQUEST_TO_PRICING,
query: a!query(
logicalExpression: a!queryLogicalExpression(
operator: "AND",
filters: {
a!queryFilter(
field: "c1",
operator: "in",
value: {0,1}
),
a!queryFilter(
field: "c20",
operator: "=",
value: ri!processId
),
a!queryFilter(
field: "c19",
operator: "=",
value:ri!txtTaskStatus
)
}
),
pagingInfo: ri!pagingInfo
)
).data.c4
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
marky
over 8 years ago
Thank you for the suggestion, but with 15,000 rows of data, selecting all will result in crashing the server. We had to delete and refresh the analytics engine after multiple queries were eating up a lot of CPU, slowing down the environment, and blocking the deletion of the processes that were being queried. We will need to just create separate task reports with only a single column, and also use paging when we need all columns, as I don't see another option to handle this much data.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel