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.
Expand your NetSuite knowledge by joining our Ask A Guru Live sessions. RSVP on this event now.
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.

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

Quick Add & Default Subsidiary

edited Nov 28, 2019 11:51AM in Accounting / ERP 1 comment

SUMMARY:   Quick Add unusable for us because records created via quick add default to the top-level subsidiary - even if the person/role creating it has no access to that subsidiary.

Quick Add (e.g., Lead) seems to create a record attached to the top-level subsidiary, even if the user creating it is not attached to that subsidiary and has no access to that subsidiary via the role the user was using.

As a result, the user cannot access the record that s/he has just created  (Permission violation: The restrictions on your role deny you access to this record)  Note that NetSuite's notice was totally unhelpful identifying the cause, so as a result I ended up spending hours trying to track down permissions, trying to figure out if it was related to sales role = yes, and playing with the "Do Not Restrict Employee Fields" and "Allow Cross-Subsidiary Record Viewing" settings -- only to find out that it was a subsidiary issue.

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