Morning All. So i am using `.setWhenOrderedBy` on ...
# suitescriptk
karlenigma
05/15/2018, 10:30 AMMorning All. So i am using
.setWhenOrderedBy Copy code
columns[1].setWhenOrderedBy({
name: 'trandate',
join: 'transaction'
});l
lukeabbott
05/15/2018, 12:40 PMI just read the docs. Are you running a customer search and then joining to the transaction record like in the example?
lukeabbott
05/15/2018, 12:41 PMI don't understand why the docs don't show this being used on a transaction search directly, you wouldn't need a join then (though you are right, it says it's required).
k
karlenigma
05/15/2018, 12:42 PMThat's what is throwing me. I checked @erictgrubaugh Search documentation and he mentiones just to put
join: 'x'karlenigma
05/15/2018, 12:45 PMI'm wondering whether i need to have the trandate column in there as a column as well.
l
lukeabbott
05/15/2018, 1:05 PMWould join '@NONE@' work?
lukeabbott
05/15/2018, 1:05 PMJust throwing something out to see if it sticks... no reason why it would work.
e
erictgrubaugh
05/15/2018, 3:50 PMsetWhenOrderedBye
errol
05/15/2018, 5:06 PM@karlenigma definitely odd that join is *required*… i see no reason it should be. However as @erictgrubaugh mentioned, there is definitely a bug in 2.0 when running searches that use the “when ordered by” function. I have only used it in script indirectly, for example I loaded an existing search and ran it. In 2.0 though, I found that the results where not being returned correctly and different than running it in the UI.
errol
05/15/2018, 5:07 PMit may work if you directly set and use setWhenOrderedBy in script, but it seems they didn’t fully think it through as they required a join field.
k
karlenigma
05/15/2018, 5:08 PMI have it on my script and defo doesn't work. Going to go down the search.load tomorrow and see it I can get my script to work that way.
e
errol
05/15/2018, 6:04 PMJust be careful with it using search.load. That I know for a fact was returning incorrect results. So be sure to check that. What I was seeing was that the number of results was correct, but the values in the column that was using “when ordered by” were not accurate. Running the same search in the UI shows the correct results.
c
creece
05/15/2018, 6:05 PMIt doesn't work when you load the search either. I can confirm that. I tried in both search.load and search.create and neither behaved correctly when using that function.
k
karlenigma
05/15/2018, 6:10 PMHow did you get around it @creece. As without using the search as it is in the UI I have little to no idea.
c
creece
05/15/2018, 6:12 PMI super wizard i work with wrote the search differently
k
karlenigma
05/15/2018, 6:14 PMHmmm don't think that will happen might have to stick with running the search and only doing it for max 75 items.
karlenigma
05/15/2018, 6:14 PMRunning the search 75 times lol
c
creece
05/15/2018, 6:18 PMYou may not have to do that if you can re-write the search but if you don't set when ordered by, you can set your sorts appropriately and loop through them
creece
05/15/2018, 6:19 PMI was about to go down that route before my coworker figured out the seardh
creece
05/15/2018, 6:25 PMif you just use MAX instead, you'll get more results, but the 1st one SHOULD be the latest if thats what you're going for.. if you group by a certain ID you can loop through results and track the ID and when you hit a new ID, grab the 1st result as the latest.. something similar to that
2 Views