CDR
05/14/2025, 6:43 PMCeligo AI
05/14/2025, 6:43 PMAI generated answer (using internal Slack threads):Based on the conversations, it seems that the issue of a custom entity field not showing up in a SuiteQL query can be due to several reasons: 1. The custom field is not storing a value: If the custom field is a Non Store Value field, you have to repeat the lookup in the query. For example, if sourcing and filtering is set to Customer : Field, you 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. 2. Permissions issue: There might be some sort of permissions issue that is preventing the field from being accessed. 3. The field is not set: The field does not show up in SuiteQL results if it's not set. You can try running a query where the custom field is equal to a valid value and it should give you a transaction. Then, query on the transaction.id and it should give you the custom field. You can check the existence of the custom field in the Setup > Records Catalog (not to be confused with the SuiteScript Records Browser). Navigate there, then switch over to the “Fields” search and see if it is missing. Here is an example of how you can query a custom field:
SELECT custbody_my_field FROM transaction WHERE id = 20804269
Replace custbody_my_field
with your custom field ID and 20804269
with a valid transaction ID.
******
Disclaimer:
This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes.
******Celigo AI
05/14/2025, 6:44 PMSlack thread 1: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.852083445
Slack thread 2: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.848611474
Slack thread 3: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.846280158
Celigo AI
05/14/2025, 6:44 PM