When Calendar Autopilot is enabled, events are automatically created and synced between Outlook and NetSuite.
However, users can still manually associate these events with additional NetSuite records, such as transactions or support cases, directly from the ExtendSync application.
💡 Keep in mind:
NetSuite only allows one transaction or support case per event.
Attempting to associate the same event with another transaction or case will create a duplicate event in NetSuite.
How to Manually Associate an Event
Let's take a look at the scenario below, the event was already saved to an opportunity record but you now want to link it to another Transaction or Support Case.
Step 1: Search for Records
Use the search box in the ExtendSync application to look up other NetSuite records you’d like to associate with the event.
You can use prefixes (like opp:, cust:, case:) to narrow your search and optimize results.
Step 2: Select and Add Record
Once you find the desired record, mark the box for the record/s to associate the event then click Add.
Step 3: Associate Event
Once you have the records added to the selections list, hit the Associate Event button. This will be saved to Communications Tab> Activities.
⚠️ Important Notes
Each time you manually associate an event with a different transaction or case, a duplicate event will be created in NetSuite.
NetSuite enforces a one-to-one relationship between calendar events and transactions/support cases.
Your NetSuite Calendar will display multiple entries of the same event — one for each manual save.
Example
In the example below:
The first event was saved and associated with an Opportunity record.
The user then manually associated it with another transaction record.
Result
Two events now appear in the NetSuite calendar.
If you open each event, you will see the details on the related records:
0001712 | Big 5 CloudExtend Outlook for NetSuite
Opp 0001739 | New Opp
Best Practices
Use Calendar Autopilot for automatic syncing and association whenever possible.
Avoid manually associating the same event with multiple transactions to prevent duplicates.
If you need to associate events with multiple entities, document the event link within your primary record (e.g., add related record references in notes).