Hello! I'm Helen from the SuiteScript team and i'm currently working on ways to help you build better custom UI on the platform. Question, if we build a drag-and-drop tool to help you build UI, where you can build the layout/field and connect to netsuite data (search, record), and export code for you. Will you use it? If so, how? If not, why? Would love to hear your thoughts! Please feel free to comment on the thread or DM me. Thanks! 🙂

Hi Helen, to clarify, are you talking about Suitelets?

I for one would use it...

Yes that will be handy 🙂

The big advantage is that it will get other users to start building other screens on top of Netsuite platform, currently new development is limited only to people with some coding/programming background.

Assuming that it spits out code we can modify, I'd likely only use it if that generated code was readable and modifiable. If it spits out a single line of minified JS and HTML with nonsensical IDs and such, I'd likely avoid it.

Agree with @erictgrubaugh ! It would have to be a 'helper' not a standalone thing.

@Lea CC yes, Suitelet, potentially form customization as well

I’m a partner who build suiteapps and one off PS development in customers accounts. I’d like it to work similar to the Visual Studio Forms Editor where the XML corresponds to the elements on the suitelet/form. That’s in a perfect world :)

@Ankur Sanghi @erictgrubaugh right it will generate readable and modular code to help you kick-start your project.

It looks like that 🙂

what do you like about this form editor? @ERP Experts

@helen I like how simple it is to place something, and change the order of it. Also the ability to set properties etc on it via the UI. Having the Editor generate the XML etc, and then be able to load it back up again to make changes quickly and easily would be exceptionally handy!

Coming from the JS world I would much prefer an HTML/CSS based layout over an XML/XSLT one. Also that would likely be more consistent with SuiteCommerce

I would love a way to load a single global css and JavaScript file that I controlled and was available everywhere. I find I create a lot of small UI widgets, primarily for navigation, and a small set of available scoped classes and ids with a little JS for interaction would go a long ways.

@Timothy essentially you want to add custom components into the visual builder. is that right?

@helen I wasn’t thinking so much about the visual builder. I would be a hard sell on a drag and drop UI tool. I was thinking about account level JS and CSS files. There are a crazy number of articles out there about hacking the UI and it seems like this is where a lot of the UI creativity comes from. If you remove the necessity of hacking the UI and using undocumented features to get basic functionality, you’ll get a lot more high quality UI development without building a custom tool. That plus updated documentation on existing features and apis would go a long ways. It’s using SuiteScript when necessary, but for basic UI, it’s more about getting SuiteScript out of the way.