# User Event execution not triggered after import

**URL:** <https://connective.celigo.com/t/user-event-execution-not-triggered-after-import/3816>\
**Category:** Integrator.io\
**Tags:** netsuite\
**Created:** [March 14, 2025, 3:17pm UTC](https://connective.celigo.com/t/user-event-execution-not-triggered-after-import/3816 "2025-03-14T15:17:17Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![tylerlamparter](https://sea1.discourse-cdn.com/flex001/user_avatar/connective.celigo.com/tylerlamparter/32/9204_2.png) [@tylerlamparter](https://connective.celigo.com/u/tylerlamparter)\
**Post date:** [March 14, 2025, 3:41pm UTC](https://connective.celigo.com/t/user-event-execution-not-triggered-after-import/3816/2 "2025-03-14T15:41:51Z")

</div>

There is a good response here from @muneswarathotakura on when we use submitField vs submitRecord:

> [@NetSuite record.submitFields() vs record.save()](https://connective.celigo.com/t/netsuite-record-submitfields-vs-record-save/48/2):
>
> Hi Bas van Ditzhuijzen, In NetSuite import we use submitField and SubmitRecord efficiently based on the below scenarios. For record creation, transformation, multi-select fields, text fields (Dropdowns, Multi-Selects), subrecords, sublists, and when working with unsupported submitField record types —submitRecord should be used, as NetSuite Nlapi does not support these actions with submitField. However, when updating body fields, it is recommended to use submitFields. This approach minim…

---

_[View the full topic](https://connective.celigo.com/t/user-event-execution-not-triggered-after-import/3816)._