This topic contains 14 replies, has 0 voices, and was last updated by pcutler 6 years, 10 months ago.

  • Author
    Posts
  • #18455

    gerson.rodriguez

    Hello All,

    I’m Gerson Rodriguez, Manager Product Management Platform, I’m leading SuiteScript PM organization and I want to hear from you. Yes, this is for real and I will be replying to your requests here. So bring it on! Again, this is about functionality that you wished you had in SS 1.0 and that you still don’t get in SS 2.0.

    P.S. Tell your colleagues and friends in the community that Santa is listening!
    This is a cached copy. Click here to see the original post.

  • #18456

    pcutler

    Thanks for asking, I’m sure the community will have lots of good ideas.

    To kick off the discussion, how about control over the time-out when making a web request?

  • #18457

    gerson.rodriguez

    Thanks Phil, this one goes on top!

  • #18458

    MikeBucklaew

    Hi Gerson –

    I know SuiteAnalytics is in the middle of being enhanced and I’m wondering if there will be a new SuiteAnalytics API to go with it. It was a nice idea in 1.0 but was too limited in functionality to be truly usable. Being able to add filter drop-downs and things like that would be great

    Thanks for asking


    gerson.rodriguez replied on 12/10/2017, 07:08 PM: Thanks Mike for your contribution. It would be good to get more details on your request. We could start here and then schedule a call. But yes you can expect a expanded effort in playing along with SuiteAnalytics.

  • #18459

    teddycaguioa

    Browser-side caching of SS2.0 module files when used on client scripts.


    gerson.rodriguez replied on 12/10/2017, 07:08 PM: Hi Teddy,

    Noted!

  • #18460

    j.j

    nlapiCreateReportDefinition – report definition and creating reports – particularly matrix reports that use netsuite reporting engine would surely help – we have many ss1 scripts utilizing report definition and pivot opbjects. also if something can be done for graphical representation in SS2 it would be great


    gerson.rodriguez replied on 12/11/2017, 10:52 AM: Thanks JJ. I need to take a closer look at this one but I will get back to you.

  • #18461

    MChammaTX

    I would say the Date APIs from 1.0. I know for most it is not a big deal and others use moment.js and still others found a hidden server side module called util/date in some data centers. I’ve ported over the underlying 1.0 API code to 2.0 but I still find it annoying.

    Also am I correct in understanding there is no nlapiYieldScript in 2.0 since the 2.0 solution is to use map/reduce? How about nlapiYieldScript for scheduled scripts in 2.0 to give us more options?


    gerson.rodriguez replied on 12/11/2017, 10:53 AM: Are you saying that you would like the date API from 1.0 on 2.0 ?

  • #18462

    tgrimm

    nlapiYieldScript should be the number one ask on this board! Map/Reduce is great in certain circumstances but has its own limitations outside of being a giant pain to debug. Many times a process is created as a scheduled script initially because the amount of processing required is not all that complex but 2 months down the road the demand has significantly increased now causing governance issues.

  • #18463

    pcutler

    How about the ability for fields created dynamically via SuiteScript to use filtering, or, if possible, the ability to dynamically add filtering to existing standard/custom fields in the before load user event? There seem to be a lot of questions requesting that on this forum, so that addition could push a lot of users toward SS 2.0.

  • #18464

    MChammaTX

    I don’t remember the use case but a few times it would have been handy to know the data type of various fields. Perhaps some meta data can be included in the record.getFields() call, instead of just returning the string of the fieldid, also include the data type.

  • #18465

    TheUsualSuspect

    Better ability to control field display types. Current method involves modifying attributes “isDisabled”, “isHidden” on the object instead. For line level fields the object won’t exist until a line is added.

  • #18466

    jmacdonald

    I’ve had 2 support cases in the last week where I have been attached to a defect and told to use SS1 to get around the issue. I think defects need to be taken more seriously and after being identified should be pushed to the top of the list for next release, new features are great but fixing stuff that is supposed to be in SS2 but is broken would be my number 1 priority.

    My first issue was amending an Inventory Adjustment with a Serialized Item in a User Event Before Submit caused the Inventory Details for that item to be cleared, causing an error about not having set Inventory Details.

    My second issue was using the getLineCount method on a subrecord from a sublist line, I was told this would work in a User Event script or by using SS1. Checking the code myself in the browser revealed that the only issue was a missing ‘options’ parameter, I included this in the case and was informed that the urgency was U6 – Candidate for a Future Feature Release, which seems crazy for such a minor change.

    Some other things that may be good to move over from SS1 to SS2 would be the setSublistValues on suitelets which allows multiple lines to be set in one operation rather than looping through all lines. Also the nlapiRequestURLWithCredentials method does not seem to have a SS2 equivalent which surprises me. Finally, having an update/fix of some documentation would be beneficial as some of the example contain code that doesn’t match the methods, even more worrying is that some of the example contains code that works but the documentation shows another way which doesn’t actually work!


    TheUsualSuspect replied on 12/29/2017, 11:03 AM: I have had similar experiences. I have opened multiple defects with respect to the search module paged search functions. Searches will return incorrect or inconsistent results leaving out search results. These have been scheduled as U6 as well.

  • #18467

    MChammaTX

    Another major pain for me has been working with ui dialog and message. They all run asynchronoulsy which make them useless for client side validation, which is like 50% of the use cases. Can NetSuite provide a synchronous option to display these. Dialog looks SO much better than alert.


    gerson.rodriguez replied on 12/29/2017, 09:13 PM: We will look into it. Thanks for you for your input.

  • #18468

    michoel

    Originally posted by MChammaTX

    View Post

    Another major pain for me has been working with ui dialog and message. They all run asynchronoulsy which make them useless for client side validation, which is like 50% of the use cases. Can NetSuite provide a synchronous option to display these. Dialog looks SO much better than alert.

    +1, but I think instead of a synchronous dialog box, you should be able to return a promise to the validate functions.

  • #18469

    pcutler

    Originally posted by MChammaTX

    View Post

    Another major pain for me has been working with ui dialog and message. They all run asynchronoulsy which make them useless for client side validation, which is like 50% of the use cases. Can NetSuite provide a synchronous option to display these. Dialog looks SO much better than alert.

    Or as an alternative, how about an API method for submitting the form.

You must be logged in to reply to this topic.