Discussions
Stay up-to-date with the latest news from NetSuite. You’ll be in the know about how to connect with peers and take your business to new heights at our virtual, in-person, on demand events, and much more.
Review our AI Community Guidelines before posting AI-generated or AI-assisted content. Verify accuracy and include the appropriate AI disclaimer.
Keep an eye out for upcoming NetSuite events, including meetups, workshops, and webinars. These sessions are a great way to connect with peers, learn from experts, and stay current on the latest NetSuite updates and best practices. Registration links are provided in each event.
Ready for Next starts at SuiteWorld
SuiteWorld is where the NetSuite community comes together to learn, connect, and discover what’s next.
Whether you’re looking for product updates, practical tips, new ways to improve efficiency, or insights from other customers, SuiteWorld offers something for every stage of your NetSuite journey.
SuiteWorld is where the NetSuite community comes together to learn, connect, and discover what’s next.
Whether you’re looking for product updates, practical tips, new ways to improve efficiency, or insights from other customers, SuiteWorld offers something for every stage of your NetSuite journey.
Discover new innovations across NetSuite with 2026 Release 2
■ NetSuite 2026.2 Release Notes
■ NetSuite SuiteApps Release Notes
■ NetSuite Sneak Peeks
■ Release Preview Guide
■ Release Preview Test Plan Template
■ NetSuite 2026.2 Release Notes
■ NetSuite SuiteApps Release Notes
■ NetSuite Sneak Peeks
■ Release Preview Guide
■ Release Preview Test Plan Template
Action Required: Review and submit pending reconciliation matches before the NetSuite upgrade to avoid rework. After 26.2, unsubmitted matches will be unmatched. For more details, see SuiteAnswers 1047397
Customer Survey URL Improperly Formats Customer ID
I followed the instructions at SuiteAnswers ID #9417 to create our URL for sending out the customer survey. The first 2 groups that we sent out were fine and linked back to the customer record, however now we are seeing that with "&custrecord_cust_survey_customer=${customer.entityid}" it is simply putting the customers name in the URL, which does not work because there are spaces in the customers name.
Has anyone experienced this issue before? How are you referencing your customer in the survey URL?
We also tried ${customer.internalid}, but because our field on the survey is type List/Record Customer, it doesn't recognize the ID number as a valid entry.
Tagged:
0