Whats faster: Getting two field values on a non-t...
# suitescriptd
donaldtran
12/13/2017, 6:17 PMWhats faster: Getting two field values on a non-transaction record via a saved search, or a load record?
i
igorp
12/13/2017, 6:40 PMnlapiLookupField is the way to go
d
donaldtran
12/14/2017, 11:30 PMWhen doing 1 field, I always do lookup value. What about say, 2, 3, or 4?
donaldtran
12/14/2017, 11:31 PMAt what point do i create a search instead? load a record?
i
igorp
12/15/2017, 1:11 AMYou can lookup as many fields as you want, just pass an array of field ids.
You create a search when you need results from more than 1 records or you need sublist values.
You load a record when you need to manipulate sublist values.
d
donaldtran
12/15/2017, 11:37 PMAm I missing the point or are you?
I'm not wondering how to get the values; I was wondering which is faster: LookupField on 2 fields, or LoadRecord and getValue on 2 fields? And at what breakpoint will LookupField be slower than LoadRecord?
This is for non-transaction records.
Transaction records, LookupField is usually the way to go
donaldtran
12/15/2017, 11:38 PMActually the original question was: Creating a search, or Loading the record. So I guess theres three methods now once you add LookupField
donaldtran
12/18/2017, 8:09 PMIve tested it in small amounts. It seems like LookupField is faster in almost all cases (i didnt do a
performance.now()donaldtran
12/18/2017, 8:09 PMThanks man!
i
igorp
12/18/2017, 8:14 PMLoopup field should be faster than loadRecord in 100% percent of the cases since there is no loading of the whole objRecord from DB. It's a straight up values retrieval from the DB.
Also, keep in mind that for loadRecord there could be UE which will make the loading even slower.
Anyhow, I am glad I could help.
3 Views