@jcribb uploaded a file: Untitled

But, the gist is, you add a functionName / Client Script to an object on your form in the UE script, have it trigger when in view mode, then do your N/ui/dialog or message in the Client script

@jcribb I think he is asking/wanting to trigger something in view mode without any click, based on conditions/data...

There's a more thorough example

Yeah, that link shows a couple of ways to do it without a button

Any idea why undefined

tranid

?

When is this running?

ClientScript on button Click and View Mode @erictgrubaugh

So is an existing transaction..where I see the

tranid

right on the screen...

not sure

Yes is undefined and I don't understand why is that... does not make much sense...

Then a lookupFiled would work for sure but this is entirely unnecessary the way I see it...

The beautiful solutions NetSuite make you do... (Total joke...)

speaking of that.... I nearly had a nervous breakdown trying to troubleshoot an issue yesterday before i discovered this gem.

search.LookupField

, when used on a multiselect field, will return 2 entirely different data structures, depending on the Labels/Text of the selected values. Those without any commas:

[{"value":"3091","text":"Test"},{"value":"3094","text":"Test without comma"},{"value":"3101","text":"Test 2"},{"value":"3114","text":"Test 3"},{"value":"3153","text":"Test 4"}]

Those with any commas:

{
  "value": "3091,3094,3101,3114,3153",
  "text": "Test,Test , with comma,Test 2, Test 3,Test 4"
}

That is a beauty... yesterday I end up doing a function

getLookUpData

to handle return data from

search.LookupFields

but it does not handle Multi-Select Fields as @erictgrubaugh notice and let me know, I did not even worry about that and now with @shea discovery I'm glad I did not do it...

@shea are you suggesting that it incorrectly merges values if the labels of those values contains a comma?

not really suggesting. 😄 i can produce the either of those outputs using the same script by changing the label associated with the backing list/record used by the multiselect

meh, avoid lookupFields

ha that sounds like a pretty wild defect

i didn't flip my desk over when i realized what was happening, but i was pretty close. is there a way to report it? one that doesn't involve 10 hours of convincing support?

@stalbert I love to avoid lookupFields... but in this case what you do?

tranid

is undefined...The NFT(TypeScript God) handle that?

@shea i wish lol they will probably just tell you the workaround is to use a full search, so since it has a workaround it's an enhancement

exactly. which is laughable but whatever. netsuite indeed.

😂 @alien4u can you try

var poNum = myCurrentRecord.getValue({
		fieldId: 'transactionnumber'
	});

@jkabot That give me a very funny number I don't even know what is it hahaha

PURCHORD53960

My PO Number is:

PO-350267

it worked in the account I tried it on 😞 ¯\_(ツ)_/¯

but tranid didn't work for me either when in view mode lol

Has anyone used the new query api (N/query) in script yet?