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.
Now is the time to ask your NetSuite-savvy friends and colleagues to join the NetSuite Support Community! Refer now! Click here to watch and learn more!
Update your Profile with your Support type to get your Support Type badge.
Expand your NetSuite knowledge by joining our Ask A Guru Live sessions. RSVP on this event now.
Uncover the power of data with the Analytics Hub —your ultimate guide to mastering NetSuite Saved Searches and Reports. Simplify the complex and unlock your organization's true potential. Dive into the Analytics Hub now and soar to new heights!
NetSuite 2025.2 Release Notes - This document summarizes the changes to NetSuite between 2025.2 and the previous release.
To help you get the most out of your 2025.2 Release Preview account, review the topics outlined in the 2025.2 Release Preview Guide.
SuiteWorld October 6 - 9, 2025: Agenda Builder is live!

Read on for the latest updates including:
• Agenda Builder launch
• SuiteWorld On Air registration
• New NetSuite Prompt Studio Contest
• And more!

Check out this thread to learn more!

The mysterious h Parameter

edited Dec 2, 2019 6:02PM in SuiteCloud / Customization 3 comments

We are trying to have our customers manage their email preferences in one place. It happens that this one place is a DNN site. We want to recreate the communication preferences link and frame that in the DNN site. That way no matter how they get to the page (email or the customer facing site) the preferences are the same. Less confusing that way.

So, to that end I made a suitelet that takes in a couple of custom parameters. One for the email and one for the customers internal id, both of which we have in the DNN site. Now, through trial and error we have come to the conclusion that the 'h' paramenter in the communications preference link is encrypted. We assumed it was the email for the user. Unless I am doing something wrong it is not the email. I get a very different string with nlapiEncrypt than I seeing in the URL. Here is my code:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!

Leaderboard

Community Whiz

Quarter 3 (Jul-Sep 2025)

This Week's Leaders

This Month's Leaders

All Time Leaders