Deleted Record Search Functionality in NetSuite

Deleted Record Search in NetSuite allows easy retrieval of deleted records using SuiteScript and SOAP operations.

·2 min read·View Oracle Docs

The Deleted Record Search feature in NetSuite facilitates users in locating previously deleted records efficiently, providing essential filtering options in SuiteScript. By utilizing the Records Browser, developers can explore what records support this search type and apply filters accordingly.

How Does the Deleted Record Search Work?

The Records Browser includes a Deleted Record page where you can view available columns and filters for performing deleted record searches in SuiteScript. It's important to check the page of any record you wish to filter; those that can support deleted record searches are labeled with Supports Deleted Record Search. This feature significantly enhances the ability to manage data integrity by tracking changes effectively.

Utilizing SOAP Web Services for Deleted Records

When working with SOAP web services, retrieving deleted records is conducted differently. You can use the getDeleted operation to acquire a list of records that have been deleted. This operation allows for filtering based on:

  • Record type
  • Script ID
  • Date of deletion

Each record that matches the specified criteria will return essential information such as:

  • Record type
  • Record name
  • Internal ID
  • External ID (if available)
  • Deletion date

For those synchronizing data with NetSuite, such as maintaining contact lists in client applications, leveraging getDeleted can ensure records stay up to date by reflecting changes since the last synchronization.

Permissions Required for Accessing Deleted Records

Only administrators and users with the Full Access role are granted permission by default to utilize the getDeleted operation. However, this permission can be extended to other roles. For roles to access deleted records through both the user interface and SOAP web services, the Deleted Records permission is essential and can be configured in the role settings under Setup > Users/Roles > Manage Roles. Importantly, users can still access deleted record information without permissions for creating or modifying the record type in question.

Conclusion

Understanding how to navigate and utilize the Deleted Record Search allows developers and administrators to enhance their data management practices effectively. This feature not only supports data integrity but also aids in accountability within applications linked to NetSuite.

Key Takeaways

  • The Deleted Record Search lets users efficiently locate deleted records with available filters.
  • Using the getDeleted operation in SOAP web services is crucial for managing deleted records.
  • Access permissions for deleted records can be customized for different roles within NetSuite.

Frequently Asked Questions (4)

Which NetSuite roles have default permission to use the getDeleted operation?
Only administrators and users with the Full Access role have default permission to use the getDeleted operation. However, this permission can be extended to other roles through role settings.
Can I filter deleted records by date using SOAP web services in NetSuite?
Yes, you can filter deleted records by the date of deletion using the getDeleted operation with SOAP web services.
Do I need special permissions to access deleted records through SuiteScript?
To access deleted records, the Deleted Records permission is required and can be configured for roles under Setup > Users/Roles > Manage Roles. This permission is essential regardless of whether access is needed through SuiteScript or the user interface.
How can developers find out which record types support Deleted Record Search in NetSuite?
Developers can use the Records Browser to check if a record type supports Deleted Record Search. Records that can be filtered in this way are labeled with 'Supports Deleted Record Search' on their specific pages.
Source: Deleted Record Search Oracle NetSuite Help Center. This article was generated from official Oracle documentation and enriched with additional context and best practices.

Was this article helpful?

More in Integration

View all Integration articles →