Imad
04/30/2025, 7:40 AMCeligo AI
04/30/2025, 7:40 AMAI 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. ****** The issue you're experiencing with not being able to see custom fields in SuiteQL responses, while they are visible in REST API responses, could be due to a few reasons: 1. Unsupported Fields: Not all fields are supported in SuiteQL. If the custom fields are not in the list of supported fields, they won't be accessible via SuiteQL. You can confirm this by using the Dataset Builder in NetSuite which provides a searchable list of fields. 2. Non-Stored Value Fields: If the custom field is a non-stored value field, you would need to repeat the lookup in the query. For example, if sourcing and filtering is set to Customer : Field, you would have to join on the entity and pull in that field in the query from the Customer table, and not rely on the custom field you created. 3. Permissions Issue: There could be a permissions issue preventing you from accessing the custom fields via SuiteQL. You can check this by navigating to Setup > Records Catalog in NetSuite and switching over to the “Fields” search to see if the field is missing. If none of the above solutions work, it's possible that there's a limitation with SuiteQL in accessing certain custom fields.
Celigo AI
04/30/2025, 7:40 AMSlack thread 1: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.86136657
Slack thread 2: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.857556164
Slack thread 3: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.854473114
Celigo AI
04/30/2025, 7:40 AMImad
04/30/2025, 7:55 AM