In the Base url for the customer page (<https://yo...
# ask-stanley-ai
t
In the Base url for the customer page (https://yourcompany.netsuite.com/app/common/entity/custjob.nl?id=) i want to use the "entityid" as the variable for id=, give me a tutorial on how to do that. If possible, I want it to open on the "Sales transaction" information tab. EntityID is a standard field and I do not want to use any custom javascript.
c
AI generated answer (using internal Slack threads):
Based on the conversations, it seems like you want to create a custom field that will contain a URL to the customer's page, using the entityid as a variable for the id in the URL. Here's a step-by-step guide on how to do this: 1. Navigate to the Customization > Lists, Records, & Fields > Entity Fields > New. 2. In the Label field, enter a name for your new field (e.g., "Customer URL"). 3. Set the Type to "Free-Form Text". 4. In the Applies To section, check the "Customer" box. 5. In the Display section, set the Display Type to "Inline Text". 6. In the Validation & Defaulting section, set the Default Value to a formula. The formula should be:
'<https://yourcompany.netsuite.com/app/common/entity/custjob.nl?id=' || {entityid} || '>'
. This will concatenate the base URL with the entityid of the customer. 7. Make sure the "Store Value" checkbox is unchecked. This will ensure that the URL is dynamically generated each time the customer record is accessed. 8. Save the new field. Now, when you view a customer record, you should see a new field labeled "Customer URL". This field will contain a URL that links to the customer's page, with the entityid as the variable for the id in the URL. Unfortunately, it's not possible to directly open the "Sales transaction" information tab from the URL. The tab that opens by default when you navigate to a customer's page is determined by your personal preferences in NetSuite, and cannot be controlled via the URL. ****** 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.854675293
Slack thread 2: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.834411621
Slack thread 3: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.832763672
Please provide your feedback on this answer.