Hello,
I am trying to add pv! data to a task report but it always comes out empty.
My data definition is: pv!record[W1182 Solicitud.idCategoria]
formatting: number
It does not display any information. All information I request using tp! works fine.
Am I doing it wrong? or is it not possible to display rv! info in the report?
Thank you
Discussion posts and replies are publicly visible
Hi, In the task report, its not possible to display the record variable rv! .
If you referenced a record data type as a column in the report, it will not display in the report designer; however, you can still query this data using a!queryProcessAnalytics().
Thank you Partha. I want to have a read only grid that displays active tasks but it also shows recordType information. Is that possible?
Hi Soma, thank you. When I add the data on the report and use a!queryProcessAnalytics() the data shows null for the new value. Is there something else I need to do?
I wrote a blog post about this topic: https://appian.rocks/2024/03/13/searching-for-users-in-process-reports
Record types are not supported as of now. In the past, I just added one PV of type text and just added any values to it in a semi-colon separated string.
Currently record type variables are not supported in Any Appian Reports (Task, Process or Process Model). If you want one or two record fields in your report's column you can save the value in two different Process variables in the model and access that in Report.
If you want all the fields values in record, you can follow the Stefan Helzle suggestion to add all values in a text pv
Thank you! I checked out Stefan's suggestion but I did not need all the values so this was the easiest solution.
You cannot index data from a specific record type, but if you pass the entire variable it should work. So instead of doing pv!record[W1182 Solicitud.idCategoria], just make the column pv!record. Then when you use a!queryProcessAnalytics you should see all the data there (and you can index from your expression rule / interface).
Thank you Peter, I will try this approach as it seems more sensible. I ended up creating individual pv variables and adding them to the report. I only needed 2 so it works but in the future if I need more this could make the whole process more complicated.