megaphone
Update your Profile with your Support type to get your Support Type badge.
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
Stay in the know of how NetSuite can help grow your business with our guides, webinars, and events. Subscribe Here
What Topic Should We Cover Next? Your idea could be our next feature—drop your suggestion now!
No Limits. Just possibilities. Join us for complimentary one-day events around the world and step into a future fueled by AI and limitless potential. Discover what's next at SuiteConnect Tour 2026.
Try Intelligent Payment Automation – Fee Free For Your First Month For more information, visit this thread.
Don't miss out on our Question of the Week! You only have until tomorrow, March 19, 2026, 2:00PM ET to comment your answers.

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!
Stay in the Know

Be sure you're subscribed to NetSuite communication to stay in the know about monthly happenings, updates and announcements. Subscribe

Login Fail

edited Dec 2, 2019 3:07PM in SuiteCloud / Customization 9 comments

I'm having some issues getting myself logged in and I've narrowed the problem down to the rendered login function.

I'm doing this for an AIR application using Flex Builder and the NetSuiteService.as login function shows:

public function login(login:LoginRequest):AsyncToken          {            var _internal_token:AsyncToken = _baseService.login(_login_header.applicationInfo421,_login_header.partnerInfo422,login);              _internal_token.addEventListener("result",_login_populate_results);              _internal_token.addEventListener("fault",throwFault);               return _internal_token;    }


The problem seems to arise from the reference to _login_header  which comes up null because... well it's null.  I don't see where the _login_header would get set during standard login procedure. I'm sure that I'm missing something but can't figure it out.  Any help would be appreciated.

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 1 (Jan-Mar 2026)

This Week's Leaders

This Month's Leaders

All Time Leaders