ah. There's a few options i guess. But it should b...
# suitescriptc
creece
07/21/2020, 7:19 PMah. There's a few options i guess. But it should be like you have it unless the domain is wrong. You can use N/url to get the domain and N/runtime to get the ID. Would have to do the 1.0 equivalents of that
t
toltmanns
07/21/2020, 7:20 PMmessage has been deleted
toltmanns
07/21/2020, 7:21 PMI will check docs on the equivalent. You think it's the domain then that it's picking up on?
c
creece
07/21/2020, 7:22 PMCheck out SA: 49131
creece
07/21/2020, 7:22 PMyeah it could be for sure
t
toltmanns
07/21/2020, 7:26 PMseems like this is overkill, and I am concerned that it's going to complain about the webservices url in there now...
c
creece
07/21/2020, 7:27 PMim pretty sure thats what the N/url is doing behind the scenes too
t
toltmanns
07/21/2020, 7:27 PMunless that is one of the 'safe' domains
toltmanns
07/21/2020, 7:28 PMI'll give it a shot
c
creece
07/21/2020, 7:31 PMDoc says that nlapiResolveURL that you are using returns an internal URL for the RECORD type. Using that service is "THE" way to figure out the domain unless you start doing some window.location as far as I know but what you have seems correct. What's the URL look like vs what its displaying
t
toltmanns
07/21/2020, 8:07 PMIt took way less time to add the external param to nlapiResolveUrl than to fix NetSuite's example code
toltmanns
07/21/2020, 8:08 PMthanks for the sanity check
toltmanns
07/21/2020, 8:37 PMThe only other potential issue being called out is a reference to the rest roles service, which is a valid endpoint going forward, just not typically used in NS: https://rest.netsuite.com/rest/roles
toltmanns
07/21/2020, 8:37 PMThis is a 2.0 script
c
creece
07/21/2020, 8:37 PMi didn't even see a param for it... been a long time
t
toltmanns
07/21/2020, 8:37 PMit's the 4th param
c
creece
07/21/2020, 8:37 PMyeah im not sure how often you're gonna call a netsuite restlet from a netsuite script so you probably dont need to worry about it
4 Views