Working with Field Changed Client Events
Sometimes, a change to one field triggers an automatic update to another field. For example, a change to a shipping address can trigger a change in the list of shipping methods available. In this example, the shipping address field is the controlling field, and the field that shows the list of shipping methods is the dependent field.
When working with controlling and dependent fields, be careful when using the Field Changed client event.
In NetSuite, field change events on a controlling field are triggered before a dependent field is automatically updated. If you modify the value in a dependent field using a field change script, the post-field change automatic update can override your changes.
Note that the post sourcing event handler is triggered only after the dependent field is updated by the system. Using this event will guarantee that your field changes are not overridden. Also note that the post sourcing event handler is triggered only if a dependent field exists.
For more information, see Client Script Best Practices.
For more information about controlling fields and dependent fields, see Dependent Dropdown Lists.