[savethepennies]

We are trying to get our users to associate a contact when creating a quote or opportunity. NetSuite’s default behavior is to populate the contacts list with all contacts from the selected customer record (and if there is a way to change that behavior I would love it). There are buttons on the form to “Remove All” or “Clear All Lines” but I don’t have a way to be sure the user clicks one of those. I need some way to start with a blank list and then ensure at least one contact has been selected by the user before the record can be saved.

The documentation doesn’t show contacts as an available sublist or subrecord. Does that mean I don’t have a way to modify the related contact list through scripting? Any creative ideas?
This is a cached copy. Click here to see the original post.

[leacelosacolumna]

You would have to come up with a search that will have joined fields (Contacts..). On your script you will check if the search results are more than or equal to one. You can start off by creating a saved search in the UI, use internal ID as the filter and use the Contacts joined fields on the Results tab. From there you can check if it is returning the correct results you wanted.

[savethepennies]

That is true in terms of accessing contacts in a search. We’re trying to interact with the transaction record so that wouldn’t really help.

The official answer from support is that contacts are a subrecord so what we’re trying to do can’t be done. We’ve gone another route with scripting more creative than I hoped but we can do what we need to.

[leacelosacolumna]

Contacts are not a subrecord. Subrecords are those that cannot exist independently without a parent record, which is not the case for Contacts. You can create contacts even without a parent transaction/opportunity record. The “Relationships” tab you see on the Opportunity record is more of a Related Records type. This is why I suggested to use a search with joined fields, wherein the record type you will be searching for is the Opportunity / transaction and you will use the internal ID of the current record as a filter. Therefore I don’t see it as a problem when you’re interacting with transaction record.

In any case, I might have misunderstood your problem. Would you mind sharing your solution here so I can better understand the use case?

[Author]

Posts