For any given NetSuite account, how many custom records is too many it starts causing problems?

AI generated answer (using internal Slack threads):

****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ****** There isn't a definitive answer to how many custom records is too many for a NetSuite account as it largely depends on the complexity of the records and how they are being used. However, there are a few factors to consider: 1. Performance: As the number of custom records increases, you may start to experience performance issues, especially when searching or querying these records. This is particularly true if the records are complex with many fields or if they are not properly indexed. 2. Data Management: Managing a large number of custom records can become challenging. It may be more difficult to maintain data integrity and ensure that the records are being used correctly. 3. User Experience: Having a large number of custom records can also impact the user experience. It can make the system more difficult to navigate and use effectively. In the conversations, users have reported having millions of custom records without experiencing significant issues. However, they also noted that their records were relatively simple, with few fields and no sublists or child records. If you are planning to have a large number of custom records, it's recommended to monitor the system's performance and consider strategies to manage the data effectively. This could include using a data warehouse for storing historical data, setting up processes to clean up old records that are no longer needed, or consolidating similar fields to reduce the number of custom records. Remember, the key is to balance the need for custom records with the potential impact on system performance and user experience.