seems like when connecting from matillion, seeing only label names and not script ids. seems like when connecting via non-suiteanalytics connect connections, rather via suitetalk apis, you don’t have script id schema level access, only a business layer object that is referencing labels/field names

AI generated answer (using internal Slack threads):

Based on the conversations, it seems that when connecting from Matillion, you are only seeing label names and not script IDs because Matillion is likely using SuiteAnalytics Connect or a similar tool to access the NetSuite data. SuiteAnalytics Connect provides a set of views over the actual data tables in NetSuite, which allows you to see the data but not modify it. However, these views may not include all the details you need, such as script IDs. When connecting via non-SuiteAnalytics Connect connections, such as SuiteTalk APIs, you don't have script ID schema level access. Instead, you only have access to a business layer object that is referencing labels/field names. This is because SuiteTalk APIs are designed to interact with NetSuite records and transactions at a business object level, rather than at a database schema level. If you need to access script IDs or other schema level details, you may need to use SuiteScript or SuiteQL. SuiteScript is a JavaScript-based API that allows you to create, read, update, and delete NetSuite records, while SuiteQL is a SQL-like query language that you can use to query your NetSuite data. Both SuiteScript and SuiteQL provide more detailed access to your NetSuite data than SuiteTalk APIs or SuiteAnalytics Connect. However, please note that using SuiteScript or SuiteQL may require additional coding and may not be suitable for all use cases. For example, if you need to process a large amount of data, you may need to use a Map/Reduce script or a Scheduled Script, which can handle larger data sets but may require more complex coding. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******