Discussions

Check out Oracle NetSuite upcoming events and conferences here
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!
Attention: Customers with NetSuite Electronic Bank Payment (EBP) SuiteApp, version 2020.2 QA (ID 315896) must UPDATE (do NOT uninstall) their bundle to the Production version 2022.1 (ID 416781) by December 31, 2022. Note: If users fail to manually update the Electronic Bank Payments SuiteApp within the given time window, this version of the SuiteApp (ID: 315896) will be deprecated and the account will not be updated to Leading version (2022.1) of the Electronic Bank Payments SuiteApp. Please refer to the campaign email sent to impacted customers for more information.
Update your Profile with your Support type to get your Support Type badge.
The live webinars are back! Join us on December 8, 2022 11AM - 12PM PST and learn how to Automate Key Business Process Using Set Field Value Workflow Action. For more details, click on this link.

Custom Role - Employee Restrictions

in CRM 7 comments

What is the functional difference between "none - no default" and "none - default to own"? I've read the help docs that describe the latter as "There is no restriction on what can be selected. Record access is not determined by this field. Fields of this type will select the user by default."

What are "fields of this type"? Can someone provide an example to illustrate the difference? I know I don't want any restrictions on the role I'm creating. I'm wondering if there's any benefit to the default to own setting that my users will see.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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

Leaderboard

This Week's Leaders

This Month's Leaders

All Time Leaders