for netsuite reporting purposes is it better to set up values in a list or a custom record?

AI generated answer (using internal Slack threads):

For NetSuite reporting purposes, both lists and custom records can be used, but the choice between the two depends on the specific use case and the volume of data. Custom records are more flexible and can handle a large volume of data. They can store historical data, and you can create millions of custom records without significant performance issues, as long as the records are simple with no sublists or child records. However, if the number of records is extremely high (in the range of millions), it might impact the performance, especially in the record and related records. On the other hand, lists are simpler and faster to load but might not be suitable for storing a large volume of data. They are more suitable for smaller sets of data that need to be accessed frequently. If you need to group data by certain fields (like item, month/year, location, etc.) and the reports are slow due to the large volume of data, you might consider creating a custom record with the required fields and populate it every day/night. This way, you can query the pre-calculated "table" instead of the whole system, which can improve the performance of your reports. However, if you are dealing with a large number of records that need to be updated daily, you might consider using SuiteAnalytics Dataset, which can be more performant. You can also improve the performance by putting your custom records in "container" parent records and updating the child record as a sublist. This is quicker than loading and saving each record. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******

why you are using custom records. just use suitelet.

thanks boss