updateInviteeStatus
The updateInviteeStatus operation lets users respond to NetSuite events that have been sent to them. This operation takes both the internal ID of the event as well as a calendar event status as arguments.
After invitees have responded to the event invitation, the Event record is updated with their response. Possible responses include accepted, declined, tentative, and noResponse.
Note the following:
-
For information on the Event record in SOAP web services, see Events (CalendarEvent). For general information on scheduling events in NetSuite, see Scheduling Events.)
-
There is no async equivalent for the updateInviteeStatus operation.
Note the following when using this operation:
-
Users must have a valid session. This operation includes a passport header to support request level credentials. (For information on request level authentication, see Request-Level Credentials.)
-
To update other properties on the Event record, the event owner should still use the update operation. Note, however, event owners are not exempt from using updateInviteeStatus if they have to update their own event response status. There may be cases in which event owners must decline their own event and have another person run the event for them.
-
Unlike in the NetSuite UI, invitees will not be able to send a message back to the organizer. SOAP web services does not currently support messages attached to events. An event invitee's response can include only one of the following values: _accepted, _declined, _tentative, _noResponse.
Request
The UpdateInviteeStatusRequest type is used for the request.
Element Name |
XSD Type |
Notes |
---|---|---|
eventId |
RecordRef |
References an existing instance of an Event record. |
responseCode |
CalendarEventAttendeeResponse |
The CalendarEventAttendeeResponse type includes the following enums:
|
Response
The UpdateInviteeStatusResponse type is used for the response.
Element Name |
XSD Type |
Notes |
---|---|---|
response |
WriteResponse |
Contains details on the status of the operation and a reference to the updated record. |
Faults
This operation can throw one of the following faults. See SOAP Fault Status Codes for more information on faults.
-
InvalidSessionFault
-
InvalidCredentialsFault
-
ExceededRequestLimitFault
-
ExceededUsageLimitFault
-
ExceededRecordCountFault
-
ExceededRequestSizeFault
-
UnexpectedErrorFault
Sample Code
C#
NetSuiteService nss = new NetSuiteService();
// login details omitted
UpdateInviteeStatusReference inviteeStatusRef = new UpdateInviteeStatusReference();
// Set the event id for the status update
RecordRef eventIdRef = new RecordRef();
eventIdRef.internalId = "100"; // Substitute this with your own event id
inviteeStatusRef.eventId = eventIdRef;
// Set the event status
inviteeStatusRef.responseCode = CalendarEventAttendeeResponse._accepted;
// Update invitee event status
WriteResponse resp = nss.updateInviteeStatus(inviteeStatusRef);
SOAP Request
<updateInviteeStatus xmlns="urn:messages_2017_1.platform.webservices.netsuite.com">
<updateInviteeStatusReference>
<eventId internalId="100" xmlns="urn:core_2017_1.platform.webservices.netsuite.com" />
<responseCode xmlns="urn:core_2017_1.platform.webservices.netsuite.com">_accepted
</responseCode>
</updateInviteeStatusReference>
</updateInviteeStatus>
SOAP Response
<updateInviteeStatusResponse xmlns="urn:messages_2017_1.platform.webservices.netsuite.com">
<writeResponse>
<platformCore:status isSuccess="true"
xmlns:platformCore="urn:core_2017_1.platform.webservices.netsuite.com"/>
<baseRef internalId="100" type="calendarEvent" xsi:type="platformCore:RecordRef"
xmlns:platformCore="urn:core_2017_1.platform.webservices.netsuite.com"/>
</writeResponse>
</updateInviteeStatusResponse>