NetSuite REST Azerion icon

NetSuite REST Azerion

Call NetSuite SuiteTalk REST operations.

Actions981

Inventory Count → Update record

AI-generated

Summary

Update an existing Inventory Count record in NetSuite by specifying its internal Id and the fields to modify, optionally including custom fields and controlling replacement of sublists and validation behavior.

Inputs

  • Id (required) — The internal identifier of the Inventory Count record to update.
  • Additional Fields — Optional standard fields to update on the Inventory Count record, such as Account, Class, Date, Department, Items list, Memo, Status, Subsidiary, externalId, and more, including support for sublist replacement.
  • Custom Fields — A list of custom fields to update for the Inventory Count record, each defined by a field name, type, and value appropriate to the type.
  • Debug Mode — Whether to include full request and response information in the output for debugging.
  • Authentication Method — Authentication type to use for the request, either OAuth1 (default) or OAuth2.
  • Prefer — Specifies server behavior, such as 'respond-async' for asynchronous execution.
  • X - Net Suite - Idempotency - Key — A user-defined unique key to ensure idempotent execution of asynchronous requests.
  • X - Net Suite - Property Name Validation — Sets strictness level for validating property names ('Error', 'Warning', 'Ignore').
  • X - Net Suite - Property Value Validation — Sets strictness level for validating property values ('Error', 'Warning', 'Ignore').

Output shape

A single updated Inventory Count record as returned from NetSuite REST API response, optionally including debug information if Debug Mode is enabled.

The operation performs a PATCH request to /inventoryCount/{id}. Custom fields and additional fields are flattened and sent in the request body. Sublist lines may be replaced using the 'replace' and 'replaceSelectedFields' fields. If 'respond-async' is set via 'Prefer' header, the response indicates asynchronous processing. Errors and validation behavior may vary depending on the supplied validation headers.

Links

Discussion