Applies to Riva Cloud and Riva On-Premise.
How Riva Syncs Appointments from NetSuite
Riva uses “Standard” impersonation with NetSuite. This means that Riva uses the permissions of the connection user (for example, rivasvc) to sync NetSuite data for a target user (for example, Ian Sample). A limitation embedded in NetSuite prevents one user from amending another user’s appointment, if "Event Access" for that appointment is not set to “Public”. This limitation even applies to users that are assigned to system administrator roles, unless such a user is the connection user. When Riva attempts to sync another user's appointment that is not "Public", Riva is denied access, because the connection user (unless it is an administrator) does not have the permissions of the assigned user.
This NetSuite access limitation affects how Riva can sync NetSuite appointments:
This section applies to NetSuite versions earlier than 2013.
For NetSuite 2013 and higher, see Sync private events from NetSuite 2013 or higher:
(If the connection user is the NetSuite administrator, this option is not necessary; because it is only when the connection user is not the administrator that Riva encounters permission issues to read Show as Busy and Private calendar items.)
Implementation for Riva Cloud
Implementation for Riva On-Premise
Riva On-Premise 2.4.32 added a connection option to handle "Private" and "Show as Busy" NetSuite appointment syncing. After the option has been selected and applied, Riva tries an alternate method to access the "Private" or "Show as Busy" appointments.
WARNING: Even when this option is selected, Riva might not be able to sync "Private" or "Show as Busy" NetSuite appointments to Exchange.
Article ID: 736
Last updated: 12 Feb, 2018
Also listed in
Riva On-Premise - CRM Sync -> Manage Riva On-Premise (Admin Guides) -> CRM Systems -> NetSuite CRM -> Advanced Options & Settings
Riva On-Premise - CRM Sync -> Get Started with Riva On-Premise -> Deploy Riva On-Premise -> Step 2 - Install -> Create CRM Connections -> NetSuite