are there situations where SuiteQL doesn't return data for a particular object type, but the REST API does, with the same set of permissions? For instance, Contact

AI generated answer (using internal Slack threads):

Based on the conversations provided, it appears that there are situations where SuiteQL may not return data for a particular object type, but the REST API does, with the same set of permissions. In the first thread, a user is asking about retrieving fields while executing a query using the SuiteTalk API. The response provided a link to the NetSuite help center, which explains how to execute SuiteQL queries through REST web services. This suggests that there might be some limitations when using SuiteTalk API for certain queries, which can be overcome by using REST web services. In the second thread, a user is having trouble running a SuiteQL query via the REST API due to insufficient permissions. After some troubleshooting, they discovered that the issue was related to the SuiteAnalytics Workbook permission. This indicates that permissions can affect the data returned by SuiteQL and the REST API. In the third thread, a user is trying to load a search via the SuiteTalk REST API, but they're having trouble with columns that contain formulas. The responses suggest that SuiteQL doesn't support loading existing transaction searches and that Saved Search is not supported in REST web services. However, REST web services do support SuiteAnalytics Datasets. This suggests that there might be some object types that SuiteQL can't handle, but the REST API can. In conclusion, while SuiteQL and the REST API are both powerful tools for interacting with NetSuite data, there may be situations where one tool can return data for a particular object type, but the other can't, even with the same set of permissions. It's important to understand the capabilities and limitations of each tool to ensure you're using the right one for your needs. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******