I'm deploying objects with my SuiteApp. I have a c...
# ask-stanley-ai
j
I'm deploying objects with my SuiteApp. I have a customrecord, and two record types that I use to make a dropdown on a transaction record. When I set one of those values, the internalId is saved to transaction, so when I use SuiteQL to SELECT * FROM transaction, I only have the internal id, but I need either the name or the script id to be populated in a custom field
c
AI generated answer (using internal Slack threads):
Based on the conversations, it seems like you are trying to get the script ID or name of a record type from its internal ID. The internal ID is what is saved when you select a value from a dropdown list of record types on a transaction record. However, when you query the transaction record using SuiteQL, you only get the internal ID, not the script ID or name. One solution suggested in the conversations is to use the
Scripted Record Type
instead of the
Record Type
for your dropdown list. This will allow you to get the script ID directly. You can then use sourcing to populate the script ID in a custom field. Here is a general idea of how you can do this: 1. Change the source of your dropdown list to
Scripted Record Type
. This will give you the script ID instead of the internal ID when a value is selected from the dropdown. 2. Create a new custom field on your transaction record to store the script ID. This field should be sourced from the dropdown list field. 3. When a value is selected from the dropdown list, the script ID will be automatically populated in the custom field. 4. Now, when you query the transaction record using SuiteQL, you can also select the custom field to get the script ID. Remember, this is a general idea and you might need to adjust it according to your specific requirements and the actual structure of your records and fields. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******
Slack thread 1: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.860361874
Slack thread 2: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.856513441
Slack thread 3: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.849009395
Please provide your feedback on this answer.