Note: This release is in preview. Features described here don’t become generally available until the latest general availability date that Salesforce announces for this release. Before then, and where features are noted as beta, pilot, or developer preview, we can’t guarantee general availability within any particular time frame or at all. Make your purchase decisions only on the basis of generally available products and features.

Using Your Organization’s Namespace

If your organization has set a namespace prefix, use that namespace to reference components, events, custom objects and fields, and other items in your Lightning Lightning markup.

The following items use your organization’s namespace when your organization has a namespace prefix set.

References to components that you’ve created
References to events that you’ve defined
References to custom objects
References to custom fields on standard and custom objects
References to Apex controllers
References to static resources

Support for the c namespace in organizations that have set a namespace prefix is incomplete. The following items can use the c namespace if you prefer to use the shortcut, but it’s not currently a recommended practice.

Note

References to components that you’ve created when used in Lightning markup, but not in expressions or JavaScript
References to events that you’ve defined when used in Lightning markup, but not in expressions or JavaScript
References to custom objects when used in component and event type and default system attributes, but not in expressions or JavaScript

See Namespace Usage Examples and Reference for examples of the preceding items.

Lightning Aura Components Developer Guide

Using Your Organization’s Namespace