Has anyone else encountered an issue with the N/query API where longer text field results are getting truncated?

is this a custom field? what type?

It is a field on a custom record of type long text

yeah, probably it's a current limitation of the system. There are suiteanswers articles that discusses limitations regarding character limit on search results. You can also try to mimic it on UI Saved Search.. alternate solution could just be by loading the record and getting the value.

Too bad, it's a pretty nice API. Thanks!

Thanks for the info @Ichimoku I wasn't aware of this either, just found the SA article: "The current character limit for fields on reports and searches is set at 250. Anything more than that would be truncated. This is implemented to prevent browser memory issues (example: Crashing) with large data sets."

Oh, I didn't realize that's for reports and searches! Wow.

On a separate channel, I think there was a suggestion of using .run() on search and not .runPaged(). I think that makes a difference, however I don't think that's how the N/query works lol.. the syntax is for N/search