This site was built to compliment the existing NetSuite Professionals Slack Community by adding a means for members to easily find answers to common questions and to create a searchable database of those questions and answers.

NetSuite Professionals

Hi All, Does Access level modifiers like public, private inside class will not work in Suitescript 2.1? When I use it I'm getting weird errors. Any ideas? 

class Test {
   private static instance: Test
   private constructor(){
    }
    
    static get instance(){
       
       If(this.instance){
            return this.instance();
       }

       this.instance = new Test();
       return this.instance();
     }
}

<@U02QAQB104D> basically I have implemented the singleton design pattern but the access modifiers are not supporting in Suitescript 2.1. 

If so, you need to upload your transpiled JS file, not the TS file.

I declared the instance variable type. Even though if I add instance = null; I'm seeing the same error. Do you have idea If Suitescript 2.1 supports access level modifiers ? 

Javascript does not support those modifiers AFAIK

Got it. Thankyou Shawn. I will try using typescript 

What language do you think you're coding? That looks like TypeScript (TS) to me, so you should be transpiling it to JS. That's the typical way TS is used.

This library would help you get started - it's the de-facto standard library of type definitions for NS functionality.

<https://www.npmjs.com/package/@hitc/netsuite-types>

Thanks <@U02QAQB104D> . I will try with this npm package. I got the answer.

If you want a familiar programming paradigm if you like OO, try NFT <https://github.com/ExploreConsulting/netsuite-fasttrack-toolkit-ss2>

I write all my scripts using TypeScript and a combination of OO/FP using NFT.

<@U02QAQB104D> - This NFT module is really awesome. It makes life easier. Thanks for sharing. I have one question - Does Lazy search and Governance methods will work for the results object that is returned by the sql query? 

<@UHZUXJ9BR> nay, the lazy search stuff is currently only for `N/search` style searches. Doing similar for SuiteQL searches has been brought up, and would be a nice addition. I think that at least for our team, we're using SuiteQL most often with simple searches that have less than 4000 results - and `asMappedResults` native method provides  a similar experience (though, not lazy evaluation).