This topic contains 4 replies, has 0 voices, and was last updated by benktesh 6 years, 9 months ago.
-
AuthorPosts
-
January 22, 2018 at 12:16 pm #17825
benkteshI am using a search filter to retrieve certain values (are long texts) using API 2. The returned values are being trimmed with ‘(More…)’after about 8000 characters. Is there a way to force search to return entire value? Or workaround or alternative? Is loading record is the only alternative (this will cause multiple calls)?
… columns: [
search.createColumn({
name: netSuiteIds.XXX.YYY.value
}),
This is a cached copy. Click here to see the original post. -
January 23, 2018 at 10:32 am #17826
pcutlerI haven’t seen any updated documentation on this for SuiteScript 2.0, but if I recall correctly SuiteScript 1.0 truncated search results at 4,000 characters. The only way to access the full data element was to load the record. I imagine this behavior would persist in SuiteScript 2.0 unless there have been any announcements otherwise.
-
February 5, 2018 at 11:46 am #17827
gladstoneThe truncation of longtext fields in SuiteScript 1.0 seems to have begun or changed at the end of January – we didn’t see it before then at all. It’s broken a key custom app and creates a huge problem for us – in some situations we could load a record, but in others we’d be keeping a user waiting while we load 500 or more records
NetSuite – why have you done this? What’s the use of longtext fields with such restrictions?
-
February 8, 2018 at 8:01 am #17828
benkteshSome more info:
If I use .run instead of .runPaged, I get the value. For now, I am calling lookup field if the value contains ‘more..’. I have about 2000 records with such values and should not be a big issue. But when all the values are like this, we have to deal with additional overhead and use additonal points (for restlet) calls.
-
February 8, 2018 at 8:10 am #17829
benkteshI created a case 2945298 for this issue. I hope this is resolved soon.
-
AuthorPosts
You must be logged in to reply to this topic.