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.
New AI Community Guidelines. Please review and follow them to ensure AI use stays safe, accurate, and compliant.
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.
Save $300 - limited to first 1,000 registrants
Join the NetSuite community to innovate, connect, and discover what’s next.
SuiteWorld brings thousands of innovators, builders, and leaders together to learn, connect, and shape what’s next. This October, explore how to build a stronger foundation for growth through inspiring keynotes, major product reveals, hands-on sessions, and unforgettable moments—all in one place for our biggest event of the year. Register now
Join the NetSuite community to innovate, connect, and discover what’s next.
SuiteWorld brings thousands of innovators, builders, and leaders together to learn, connect, and shape what’s next. This October, explore how to build a stronger foundation for growth through inspiring keynotes, major product reveals, hands-on sessions, and unforgettable moments—all in one place for our biggest event of the year. Register now
NSC | Why a Custom Record Cannot Be Accessed by Non-Admins
Scenario
A custom record works correctly for Administrators, but non-admin users cannot access it.
Common symptoms include:
- Users receive a permission violation error.
- The custom record does not appear in menus or global search.
- Users can see the parent record but not the related custom record.
- The record is accessible in Sandbox but not Production.
This is a common issue in SuiteBuilder because custom records require both record-level permissions and proper access configuration.
Solution
Review the custom record permissions and access settings assigned to non-admin roles.
Common causes include:
- Missing Custom Record Permissions
- Open the affected role.
- Verify the custom record type has been added under:
0