We recently changed one of our record fields from Text to Extra Long Text (We are in Appian 26.3 version). After making this change, we are no longer able to see that field in Process HQ when creating reports. This field was available before the datatype change.Does Process HQ support Extra Long Text fields for reporting? If this is a limitation, could someone point me to the relevant documentation?
I was not able to find any information about this in the documentation, so I wanted to check whether anyone has come across the same behavior.Thanks in advance!
Discussion posts and replies are publicly visible
I copied your ask into the Appian AI Chatbot. I did not get any clear output. Seems like this is not clearly documented.
Thanks Stefan.I did try checking the documentation and the Appian AI chatbot before posting, but I couldn't find a definitive answer. That's why I wanted to reach out to the community to see if anyone has experience with using Extra Long Text fields in Process HQ reporting or knows of any related limitations.
This isn’t explicitly documented for Process HQ, but official docs say Extra Long Text fields cannot be used in filters, sorts, aggregations, or records-powered components, and Appian recommends avoiding them in grids and using them only in individual record views for performance reasons.Also, based on my understanding: Process HQ reporting works only with primitive data types, and Extra Long Text is not considered a primitive typehttps://docs.appian.com/suite/help/26.5/build-best-data-fabric.html#use-extra-long-text-fields-to-store-large-volumes-of-datahttps://docs.appian.com/suite/help/26.5/query-best-practices.html#example-1https://docs.appian.com/suite/help/26.5/Appian_Data_Types.html#text
Thank you Shubham for your inputs.