I have created a "CRD column" in process report which is required to take the data from "CRD column" in User database table. I tried querying the data and indexed it but it's not populating the column with data in the process report. The column is populating null. Please suggest me alternate solution so that I can achieve this data populating.
index(rule!CP_QRY_User(
username:pv!username,
returnCdt:true,
pagingInfo:a!pagingInfo(
startIndex:1,
batchSize:1
)
),"crd",null)
i was using this expression to get data for respective column in CRD defintion in the process report.
Discussion posts and replies are publicly visible
Process reports do not support querying data. I wrote a blog post about how to add data to process reports.
https://appian.rocks/2024/03/13/searching-for-users-in-process-reports/
As Stefan mentioned querying in process reports are not gonna happen. If its just a matter of displaying in the grid, Why not do this in at the interface level, querying the complete data from the rule in a local and indexing the related value using the identifier respect to the row.
Loading too much data into an interface can lead to memory and performance issues. While this would work, I would not make it a general recommendation.
But the thing is I also need to export the data populated to export sheet and the rest of data is coming from process report. That's why I was trying to configure the field in the process report itself. Isn't there any solution so that I can make this happen?
A single call in the local variable and then using whereContains() in the row would cause performance issues too? I wasn't aware :-o
Depends on the data volume and the number of lookup cells.
Not only do process reports not support querying, as Stefan mentioned, but they handle only VERY basic / minimal expressions. That means not only no queries, it means no local variables, absolutely no expression rules that use dictionary syntax (for some reason), and no non-primitive Appian functions at that (and the kicker here is, they don't really publish what functions are "primitive" or not, you just kinda have to figure it out).
swapnilk0010 said:Isn't there any solution so that I can make this happen?
Yes - declare a new PV in your process model and do the query there, in the process flow - then point your new Process Report column at that PV value.