Is creating a domain name mandatory? - Answers - Salesforce Trailblazer Community
Trailblazer Community
Ask Search:
karthikeya abhiramkarthikeya abhiram 

Is creating a domain name mandatory?

My company is currently starting to develop salesforce lightning applications. 
I have followed the tutorials in trail head to bulid the lightning applications.
I those tutorials I came across a step where we need to create the domain name in initial stage of developing the lightning apps.

My question is Is it mandatory to create a domain name before we create a Saqlesforce lightning app.

In  a organisation , a developer will be given a  developer sandbox , where he has to work. If I create a domain name in a sandbox, is  it effetcted to overall users, I mean entire  organisation??

Please reply?
Benjamin BolopueBenjamin Bolopue
Hi Karthikeya,
As stated here (https://developer.salesforce.com/docs/atlas.en-us.lightning.meta/lightning/qs_aotp_prereq.htm):

"A namespace is not required to create Lightning components but it’s required if you plan to offer managed packages. If your org doesn't have a namespace, you can use the default namespace to access your components."

Hope this helps!

Thanks,
Ben
karthikeya abhiramkarthikeya abhiram
What is the main difference between managed and unmanaged package ? And what is best suited whether to cretae a namespace or not  , if the organisation just wanted to create an applicattion that is just used manintain the sales ?
 
Benjamin BolopueBenjamin Bolopue

Hi Karthikeya,

A package is a container for something as small as an individual component or as large as a set of related apps. After creating a package, you can distribute it to other Salesforce users and organizations, including those outside your company.Packages come in two forms—unmanaged and managed:

Unmanaged packages
Unmanaged packages are typically used to distribute open-source projects or application templates to provide developers with the basic building blocks for an application. Once the components are installed from an unmanaged package, the components can be edited in the organization they are installed in. The developer who created and uploaded the unmanaged package has no control over the installed components, and can't change or upgrade them. Unmanaged packages should not be used to migrate components from a sandbox to production organization. Instead, use Change Sets.

Managed packages
Managed packages are typically used by Salesforce partners to distribute and sell applications to customers. These packages must be created from a Developer Edition organization. Using the AppExchange and the License Management Application (LMA), developers can sell and manage user-based licenses to the app. Managed packages are also fully upgradeable. To ensure seamless upgrades, certain destructive changes, like removing objects or fields, can not be performed.

Managed packages also offer the following benefits:
  • Intellectual property protection for Apex
  • Built-in versioning support for API accessible components
  • The ability to branch and patch a previous version
  • The ability to seamlessly push patch updates to subscribers
  • Unique naming of all components to ensure conflict-free installs

Read more at: https://help.salesforce.com/apex/HTViewHelpDoc?id=sharing_apps.htm&language=en

Thanks,
Ben