Jarrett Parr is a Financial Systems Implementer for SuiteDynamics, a NetSuite solutions provider. He enjoys analyzing and improving processes for both our company and clients. He also loves solving accounting and financial problems for growing businesses. Jarrett lives in Madison, WI, with his wife, Abbie, and their golden retriever, Clark.
How to Document NetSuite Custom Objects When Merging Environments
Combining ERPs can get tricky. Here's how to tackle redundancies.
Suppose your company acquires another business that operates on its own enterprise resource planning (ERP) system. Obviously, no organization needs—or wants—two completely different ERPs.
So, you must consolidate. During that consolidation, you need to document all NetSuite custom objects in your instance to eliminate redundancies and identify any items that will transfer to your new system. It’s a practical necessity.
In this case, the term “custom object” can refer to any of the following.
- Search
- Custom Record Field
- Subsidiary
- Mass Update
- Scripts
- Entity Field
- List
- User Role
- Entry Form
- Workflow
- Bundle
- Body Field
- Column Field
- Standard Field
- Records
- Other Field
- Item Field
- Location
- Transaction Form
- CRM Field
- Department
- Class
You can use the Netwrix Flashlight by Strongpoint for NetSuite for documentation. It’s a third-party NetSuite bundle that uses a “spider” to crawl all objects in your system’s environment. A spider is an automated program that examines and indexes your entire instance, identifying NetSuite custom objects as it goes. A spider may take several days to complete its task.
How to Document NetSuite Custom Objects
First, download the Flashlight Bundle. Then, click the SuiteApps menu and type “Flashlight” in the search bar.
Click the Flashlight icon and install the bundle.
Wait for the Flashlight bundle to finish installing. Then, you will see a new Flashlight menu in your NetSuite header.
Navigate to Flashlight>Tools>Spider. Then, run the spider.
*Warning* After starting the spider, you can’t navigate away from the page until the indexing process ends. The process could last 15 minutes to over an hour.
You may also see an error message, “The Number of Rows in List Segments needs to be set to 1,000.” Fix the issue by navigating to Home>Set Preferences. Then, click on the Number of Rows in List Segments field under the Optimizing NetSuite section. Change the number to 1,000. Click Save.
Navigate back to the spider and run it. When the indexing is done, your screen will display an “Indexing complete at DD/MM/YYYY” message. You can now leave the page, even though the spider has not crawled all items yet. It has only indexed them.
Check the spider’s status on the Flashlight Overview page under the Spider Status portlet. The program is finished when the Spider Status says “Done.” The portlet will also show the completion date for the last spider crawl.
Next, navigate to Flashlight>Customization>Customization List.
Ensure the filter is set to Strongpoint Filter. The setting provides a list of every NetSuite custom object in the instance.
Then, export the list to Excel. You’ll receive a report identifying whether an object is in use, its purpose, and whether it should be transferred to your new NetSuite environment.
You can also click View to see the object’s Flashlight record. This duplicate record contains helpful information about the real record, such as the record type and its related NetSuite custom objects. It also includes a direct link to the actual record.
Need More NetSuite Tips?
A NetSuite ERP can revolutionize your business—but only if you know how to use it. SuiteDynamics Managed Services plans include one-on-one and group training sessions that can help your team get the most out of your NetSuite investment. We’ll teach you more about NetSuite custom objects, custom segments, dashboards and reports, and any other tools you need to succeed. Contact us to start maximizing your system’s potential.
Job shop manufacturing is a production method where small batches of 1-100 units of customized or unique products are made to meet specific customer requirements. Unlike mass production, each order typically requires unique setups, specialized processes, and custom routing through the facility. In this comprehensive guide, you'll learn: The complete definition of job shop manufacturing How job shops differ from other manufacturing types Industries that rely on job shop methods Technology solutions that optimize job shop operations When to consider implementing specialized ERP systems What is Job Shop Manufacturing? (Definition) Job shop manufacturing is a production strategy focused on customization over volume . Instead of producing thousands of identical items, job shops create small quantities of unique products tailored to specific customer specifications. Key defining characteristics: Small batch sizes - Typically 1-100 units per order High product variety - Hundreds or thousands of different products Custom specifications - Each order has unique requirements Project-based workflow - Work orders last days to weeks Skilled labor - Requires specialized expertise and flexibility Job Shop is a powerful, fully integrated solution built for custom manufacturers, combining quoting, configuration, production, and fabrication workflows inside NetSuite. Learn more about SuiteDynamics' NetSuite Job Shop for Manufacturing.
Uncover the challenges of data quality affecting DIO accuracy, from ghost inventory to inconsistent formats. Find out how to tackle these issues effectively with a NetSuite ERP.
In the world of private equity, creating operational value has become increasingly critical as the market evolves. With exit timelines extending and competition for deals intensifying, PE firms are looking beyond financial engineering to drive returns. One emerging strategy that's gaining traction is the consolidation of NetSuite instances across portfolio companies. The Hidden Challenge of System Fragmentation As PE portfolios grow through acquisition, a common pattern emerges: multiple portfolio companies operating on separate NetSuite instances. While each system may work effectively in isolation, the fragmentation creates significant operational inefficiencies at the portfolio level: Redundant Licensing Costs: Each separate instance requires its own licensing structure , creating unnecessary expenses that directly impact EBITDA. Manual Consolidation Effort: Finance teams spend countless hours extracting, transforming, and manually consolidating data from disparate systems. Inconsistent Processes: Basic business functions are handled differently across portfolio companies, limiting standardization efforts. Limited Portfolio-Wide Visibility: Gaining insight across the entire portfolio requires extensive manual effort, delaying strategic decision-making. Integration Challenges: Onboarding new acquisitions becomes increasingly complex when each company maintains its own environment.
Explore Esusu's partnership with SuiteDynamics to enhance financial processes. Schedule a consultation to see how your business can thrive with NetSuite solutions.
Discover how to effectively set up and configure case statuses, rules, types, priorities, and more in NetSuite's case management system. Streamline your workflow and improve customer support with this comprehensive guide.
Backorders disrupt revenue and frustrate customers. Learn what "backordered" means, how backorders happen, their impact on businesses, and how NetSuite ERP can minimize the issues.
Start simplifying finances now! Read our step-by-step tutorial on how to reconcile your credit card statements swiftly & accurately in NetSuite.
Get step-by-step instructions for accepting customer payments, making deposits, matching bank data, and completing a bank reconciliation in NetSuite.
Many businesses need complex accounting systems to maintain cash flows. Discover how switching from QuickBooks to NetSuite can create the financial stability you need.
Simplify your financial management with NetSuite Bank Feeds automation. Follow this tutorial and get started in no time.
