This topic contains 7 replies, has 0 voices, and was last updated by ajrey77 7 years, 2 months ago.

  • Author
    Posts
  • #23153

    ajrey77

    I have created an online custom record form that has a client script and a suitelet running against it that allows the end user to enter a value on the form, the client script then triggers the suitelet to preform a search and return specific fields to the online form for use by the end user. The end user can then populate additional data in blank fields on the form with the intention to update the record on submit. One of the issues I have encountered has been the custom record field "ID". I had to parse the value to remove the prefix in order to search against the internal id because I was getting a null value when searching against the ID field. Is there some characteristic of the Custom Record field "ID" (internal id: name) that is factoring into how the online form searches for duplicates before creating a new record on submit instead of updating the existing record? What solutions do you suggest for getting around this issue to allow updates to be saved to the existing custom record?
    This is a cached copy. Click here to see the original post.

  • #23154

    Olivier Gagnon NC

    I'm not sure I fully understand your question, but the ID is unique to every created record and so would not factor at all if you're trying to dedupe.

  • #23155

    k_dunc

    When you set up your Online Form, and you select the fields that you want to use in the Online Custom Record Form, have you selected any fields in the "Search" column? Is that what you're wanting to know? I'm a little with Olivier Gagnon NC on this as I'm not 100% sure what you're asking.

  • #23156

    ajrey77

    I have identified the fields I want to search on in the Online Custom Record Form configuration but when a record is submitted the search functionality isn't executing and a duplicate record is being created. I am trying to identify if there could be any issue around the search functionality on the Custom Record ID because of the configuration on the Numbering tab on the Custom Record Type.

  • #23157

    Olivier Gagnon NC

    If I understand correctly, you are using a custom script to perform a duplicate record check. As such, any potential issue with Custom Record ID would be due to an issue in your script. It all depends on how you implemented your deduping logic.

  • #23158

    ajrey77

    I have a form level client script on the Online Form that calls a Suitelet. The client script captures a value entered in the form and passes that value to the Suitelet which then performs a search on that value and returns the value of two fields from the record that are then passed back to the client script and populated in the Online Custom Form. The user can then add data to other fields on the Online Form and then submit it; at which point I was hoping that NetSuite's field search setting on the form would trigger a duplicate record check before creating a duplicate. I don't have any custom duplicate record checking coded into my client script. Should I?

  • #23159

    girieshg

    ajrey77 The duplicate check when using an online form for a custom record that allows ID (name) is vanilla NetSuite. It should work without any additional scripting or workflows, especially for the Name / ID field.

    Originally posted by ajrey77

    View Post

    I had to parse the value to remove the prefix in order to search against the internal id because I was getting a null value when searching against the ID field.

    Is your script setting the parsed value in the Name / ID field on the online form? If yes, then the system will not detect a duplicate since the Name / ID without a prefix doesn't match any existing record. Is this what you're asking about, or have I completely misunderstood your question?

  • #23160

    ajrey77

    My script is parsing the ID for searching purposes only. It does not return that value to the online form, it is returning other fields to the form.

You must be logged in to reply to this topic.