I am trying to create a text column with properties from the user function inside a process report.
I want to create a text field with "firstName lastName". I want to utilize tp!owner or the tp!assignees
The user function is suppose to be compatible with reports but when I try to use it doesn't return anything.
Discussion posts and replies are publicly visible
You'll need to remember that tp!assignees, at least, is by default a "list of user or group", and thus you'd need to do some more fiddling with whatever its value holds before being able to call any functions on it in a meaningful way. The back-end logic in reports is old, and the quirks/exceptions/special cases are not very well documented (most of the ones I know about were found just by trial and error), so this is always a touchy thing to try and mess with - especially so because using any rules/functions in the display logic is touchy, and some just plain don't work.
(edit to add: i also confirm that user() doesn't seem to work at all even after controlling for the stuff I mentioned above, though I'm not very surprised by this.)
Depending on the end result you're after, I'd more strongly recommend querying the information into a SAIL form and then displaying "friendly" information there on a row-by-row basis, which is comparatively very easy.
Thank you for the reply and confirmation. According to the documentation the user function is supported in process reports - Based on our tests - it's not.
johnf9317 said:According to the documentation the user function is supported in process reports - Based on our tests - it's not.
Do you happen to have a quick link to the documentation on that? I have done some light searching and have not found any references.
For the entire history of Appian to this point, fn!user() and other functions have been unavailable in Process and Task Reports coming from memory. In the old days where in-memory reporting was the only option really, we would save all data points that might be needed into process variables to be used directly in the reports.
These days, we persist all process information to the DB always, and report with a!queryEntiy(), minus a few light task reports that do not really need data conversions, filtering, sorting etc.
I missed that, thanks!
That probably should be reported via support ticket..