Mixing
Dynamically create a lightning component and put it into a custom lightning component
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
7
down vote
favorite
Is it possible to dynamically create a lightning component and put it into a custom lightning component?
For example, I have the following custom lightning component:
<aura:component>
<div class="wasCreatedDynamicallyInCode">
Here should go the component:
<div id="addALightningComponentHere">
</div>
</div>
</aura:component>
And I have a component which statically I would add in the following way:
<aura:component>
<div class="wasCreatedDynamicallyInCode">
Here should go the component:
<div id="addALightningComponentHere">
<namespace:MyComponent myArg="!v.myArg"/>
</div>
</div>
</aura:component>
How could I add the line <namespace:MyComponent myArg="!v.myArg"/> dynamically from client-side controller?
I am aware of everything written here. It does not help me to solve the problem, so I am posting it here.
UPDATE
In order to show why addition of !body confuses me I will tweak the code a little bit.
<aura:component>
<div class="wasCreatedDynamicallyInCode">
Here should go the first component:
<div id="addALightningComponentHere1">
<namespace:MyComponent myArg="!v.myArg"/>
</div>
</div>
<div class="wasCreatedDynamicallyInCode">
Here should go the second component:
<div id="addALightningComponentHere2">
<namespace:MyComponent myArg="!v.myArg"/>
</div>
</div>
</aura:component>
Not only the component I am setting in place of !v.body, but also the !v.body and aura:id for encompassing element should be generated at runtime.
lightning-components lightning dynamic
asked Sep 9 at 17:19
hellohowdoyoudo
654
New contributor
hellohowdoyoudo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
 |Â
show 2 more comments
up vote
7
down vote
favorite
Is it possible to dynamically create a lightning component and put it into a custom lightning component?
For example, I have the following custom lightning component:
<aura:component>
<div class="wasCreatedDynamicallyInCode">
Here should go the component:
<div id="addALightningComponentHere">
</div>
</div>
</aura:component>
And I have a component which statically I would add in the following way:
<aura:component>
<div class="wasCreatedDynamicallyInCode">
Here should go the component:
<div id="addALightningComponentHere">
<namespace:MyComponent myArg="!v.myArg"/>
</div>
</div>
</aura:component>
How could I add the line <namespace:MyComponent myArg="!v.myArg"/> dynamically from client-side controller?
I am aware of everything written here. It does not help me to solve the problem, so I am posting it here.
UPDATE
In order to show why addition of !body confuses me I will tweak the code a little bit.
<aura:component>
<div class="wasCreatedDynamicallyInCode">
Here should go the first component:
<div id="addALightningComponentHere1">
<namespace:MyComponent myArg="!v.myArg"/>
</div>
</div>
<div class="wasCreatedDynamicallyInCode">
Here should go the second component:
<div id="addALightningComponentHere2">
<namespace:MyComponent myArg="!v.myArg"/>
</div>
</div>
</aura:component>
Not only the component I am setting in place of !v.body, but also the !v.body and aura:id for encompassing element should be generated at runtime.
lightning-components lightning dynamic
asked Sep 9 at 17:19
hellohowdoyoudo
654
New contributor
hellohowdoyoudo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Yes it is and the link you have included includes the relevant material. Where are you stuck?
– Keith C
Sep 9 at 17:36
@KeithC, could you, please, provide a JavaScript code to accomplish this? Since I can follow only examples in documentation and do not know how to add the component without having a!v.body.
– hellohowdoyoudo
Sep 9 at 17:37
What is stopping you adding a!v.body?
– Keith C
Sep 9 at 17:39
@KeithC, I can have multiple places in my custom lightning component where I would like to add another lightning component. Let me update the question to elaborate this.
– hellohowdoyoudo
Sep 9 at 17:49
You're allowed to have more than one facet (attribute of typeAura.Component), beyond justv.body.
– David Reed
Sep 9 at 17:59
 |Â
show 2 more comments
up vote
7
down vote
favorite
up vote
7
down vote
favorite
Is it possible to dynamically create a lightning component and put it into a custom lightning component?
For example, I have the following custom lightning component:
<aura:component>
<div class="wasCreatedDynamicallyInCode">
Here should go the component:
<div id="addALightningComponentHere">
</div>
</div>
</aura:component>
And I have a component which statically I would add in the following way:
<aura:component>
<div class="wasCreatedDynamicallyInCode">
Here should go the component:
<div id="addALightningComponentHere">
<namespace:MyComponent myArg="!v.myArg"/>
</div>
</div>
</aura:component>
How could I add the line <namespace:MyComponent myArg="!v.myArg"/> dynamically from client-side controller?
I am aware of everything written here. It does not help me to solve the problem, so I am posting it here.
UPDATE
In order to show why addition of !body confuses me I will tweak the code a little bit.
<aura:component>
<div class="wasCreatedDynamicallyInCode">
Here should go the first component:
<div id="addALightningComponentHere1">
<namespace:MyComponent myArg="!v.myArg"/>
</div>
</div>
<div class="wasCreatedDynamicallyInCode">
Here should go the second component:
<div id="addALightningComponentHere2">
<namespace:MyComponent myArg="!v.myArg"/>
</div>
</div>
</aura:component>
Not only the component I am setting in place of !v.body, but also the !v.body and aura:id for encompassing element should be generated at runtime.
lightning-components lightning dynamic
asked Sep 9 at 17:19
hellohowdoyoudo
654
New contributor
hellohowdoyoudo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Is it possible to dynamically create a lightning component and put it into a custom lightning component?
For example, I have the following custom lightning component:
<aura:component>
<div class="wasCreatedDynamicallyInCode">
Here should go the component:
<div id="addALightningComponentHere">
</div>
</div>
</aura:component>
And I have a component which statically I would add in the following way:
<aura:component>
<div class="wasCreatedDynamicallyInCode">
Here should go the component:
<div id="addALightningComponentHere">
<namespace:MyComponent myArg="!v.myArg"/>
</div>
</div>
</aura:component>
How could I add the line <namespace:MyComponent myArg="!v.myArg"/> dynamically from client-side controller?
I am aware of everything written here. It does not help me to solve the problem, so I am posting it here.
UPDATE
In order to show why addition of !body confuses me I will tweak the code a little bit.
<aura:component>
<div class="wasCreatedDynamicallyInCode">
Here should go the first component:
<div id="addALightningComponentHere1">
<namespace:MyComponent myArg="!v.myArg"/>
</div>
</div>
<div class="wasCreatedDynamicallyInCode">
Here should go the second component:
<div id="addALightningComponentHere2">
<namespace:MyComponent myArg="!v.myArg"/>
</div>
</div>
</aura:component>
Not only the component I am setting in place of !v.body, but also the !v.body and aura:id for encompassing element should be generated at runtime.
lightning-components lightning dynamic
lightning-components lightning dynamic
asked Sep 9 at 17:19
hellohowdoyoudo
654
New contributor
hellohowdoyoudo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Sep 9 at 17:19
hellohowdoyoudo
654
New contributor
hellohowdoyoudo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited Sep 9 at 18:14
asked Sep 9 at 17:19
hellohowdoyoudo
654
New contributor
hellohowdoyoudo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Sep 9 at 17:19
hellohowdoyoudo
654
asked Sep 9 at 17:19
hellohowdoyoudo
654
654
New contributor
hellohowdoyoudo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
hellohowdoyoudo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
hellohowdoyoudo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Yes it is and the link you have included includes the relevant material. Where are you stuck?
– Keith C
Sep 9 at 17:36
@KeithC, could you, please, provide a JavaScript code to accomplish this? Since I can follow only examples in documentation and do not know how to add the component without having a!v.body.
– hellohowdoyoudo
Sep 9 at 17:37
What is stopping you adding a!v.body?
– Keith C
Sep 9 at 17:39
@KeithC, I can have multiple places in my custom lightning component where I would like to add another lightning component. Let me update the question to elaborate this.
– hellohowdoyoudo
Sep 9 at 17:49
You're allowed to have more than one facet (attribute of typeAura.Component), beyond justv.body.
– David Reed
Sep 9 at 17:59
 |Â
show 2 more comments
Yes it is and the link you have included includes the relevant material. Where are you stuck?
– Keith C
Sep 9 at 17:36
@KeithC, could you, please, provide a JavaScript code to accomplish this? Since I can follow only examples in documentation and do not know how to add the component without having a!v.body.
– hellohowdoyoudo
Sep 9 at 17:37
What is stopping you adding a!v.body?
– Keith C
Sep 9 at 17:39
@KeithC, I can have multiple places in my custom lightning component where I would like to add another lightning component. Let me update the question to elaborate this.
– hellohowdoyoudo
Sep 9 at 17:49
You're allowed to have more than one facet (attribute of typeAura.Component), beyond justv.body.
– David Reed
Sep 9 at 17:59
Yes it is and the link you have included includes the relevant material. Where are you stuck?
– Keith C
Sep 9 at 17:36
Yes it is and the link you have included includes the relevant material. Where are you stuck?
– Keith C
Sep 9 at 17:36
@KeithC, could you, please, provide a JavaScript code to accomplish this? Since I can follow only examples in documentation and do not know how to add the component without having a
!v.body.– hellohowdoyoudo
Sep 9 at 17:37
@KeithC, could you, please, provide a JavaScript code to accomplish this? Since I can follow only examples in documentation and do not know how to add the component without having a
!v.body.– hellohowdoyoudo
Sep 9 at 17:37
What is stopping you adding a
!v.body?– Keith C
Sep 9 at 17:39
What is stopping you adding a
!v.body?– Keith C
Sep 9 at 17:39
@KeithC, I can have multiple places in my custom lightning component where I would like to add another lightning component. Let me update the question to elaborate this.
– hellohowdoyoudo
Sep 9 at 17:49
@KeithC, I can have multiple places in my custom lightning component where I would like to add another lightning component. Let me update the question to elaborate this.
– hellohowdoyoudo
Sep 9 at 17:49
You're allowed to have more than one facet (attribute of type
Aura.Component), beyond just v.body.– David Reed
Sep 9 at 17:59
You're allowed to have more than one facet (attribute of type
Aura.Component), beyond just v.body.– David Reed
Sep 9 at 17:59
 |Â
show 2 more comments
1 Answer
1
active
oldest
votes
up vote
9
down vote
accepted
A Lightning attribute like v.body, which is typed as Aura.Component, is called a facet. It's perfectly legal to have multiple facets in your component.
You'd have to do something more like this, if I may modify your example component to suit. Note the Aura.Component-typed attributes: these behave like v.body in that they hold dynamically-instantiated Lightning components, but you can place them as you please and have more than one as needed.
<aura:component>
<aura:attribute type="Aura.Component" name="firstPanel" />
<aura:attribute type="Aura.Component" name="secondPanel" />
<aura:handler name="init" value="! this " action="! c.doInit " />
<div class="wasCreatedDynamicallyInCode">
Here should go the first component:
<div id="addALightningComponentHere1">
! v.firstPanel
</div>
</div>
<div class="wasCreatedDynamicallyInCode">
Here should go the second component:
<div id="addALightningComponentHere2">
! v.secondPanel
</div>
</div>
</aura:component>
Then, in your JavaScript controller, you'd do something like the below (adapted from the linked documentation, and omitting error handling and action handler body for clarity):
(
doInit : function(cmp)
$A.createComponent(
"lightning:button",
"aura:id": "findableAuraId",
"label": "Press Me First",
"onclick": cmp.getReference("c.handlePress")
,
function(newButton, status, errorMessage)
//Add the new button to the body array
if (status === "SUCCESS")
var firstPanel = cmp.get("v.firstPanel");
firstPanel.push(newButton);
cmp.set("v.firstPanel", firstPanel);
);
$A.createComponent(
"lightning:button",
"aura:id": "findableAuraId",
"label": "Press Me Second",
"onclick": cmp.getReference("c.handlePress")
,
function(newButton, status, errorMessage)
//Add the new button to the body array
if (status === "SUCCESS")
var secondPanel = cmp.get("v.secondPanel");
secondPanel.push(newButton);
cmp.set("v.secondPanel", secondPanel);
);
,
handlePress: function(component, event, helper)
)
Now, if what you need is a dynamically determined number of dynamic component slots in something like an iteration, that might be a situation that calls for decomposing this component into a suite of more elemental components (which themselves might or might not contain facets) rather than building it all into a single massive component, or following the example (again in the linked documentation) that dynamically instantiates children of dynamically instantiated components.
That said, in most cases it seems to be better design to decompose components and conditionally render rather than using very deep dynamic instantiation.
answered Sep 9 at 18:44
David Reed
19.7k21540
Decomposition works fine. Thank you.
– hellohowdoyoudo
Sep 9 at 19:41
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
9
down vote
accepted
A Lightning attribute like v.body, which is typed as Aura.Component, is called a facet. It's perfectly legal to have multiple facets in your component.
You'd have to do something more like this, if I may modify your example component to suit. Note the Aura.Component-typed attributes: these behave like v.body in that they hold dynamically-instantiated Lightning components, but you can place them as you please and have more than one as needed.
<aura:component>
<aura:attribute type="Aura.Component" name="firstPanel" />
<aura:attribute type="Aura.Component" name="secondPanel" />
<aura:handler name="init" value="! this " action="! c.doInit " />
<div class="wasCreatedDynamicallyInCode">
Here should go the first component:
<div id="addALightningComponentHere1">
! v.firstPanel
</div>
</div>
<div class="wasCreatedDynamicallyInCode">
Here should go the second component:
<div id="addALightningComponentHere2">
! v.secondPanel
</div>
</div>
</aura:component>
Then, in your JavaScript controller, you'd do something like the below (adapted from the linked documentation, and omitting error handling and action handler body for clarity):
(
doInit : function(cmp)
$A.createComponent(
"lightning:button",
"aura:id": "findableAuraId",
"label": "Press Me First",
"onclick": cmp.getReference("c.handlePress")
,
function(newButton, status, errorMessage)
//Add the new button to the body array
if (status === "SUCCESS")
var firstPanel = cmp.get("v.firstPanel");
firstPanel.push(newButton);
cmp.set("v.firstPanel", firstPanel);
);
$A.createComponent(
"lightning:button",
"aura:id": "findableAuraId",
"label": "Press Me Second",
"onclick": cmp.getReference("c.handlePress")
,
function(newButton, status, errorMessage)
//Add the new button to the body array
if (status === "SUCCESS")
var secondPanel = cmp.get("v.secondPanel");
secondPanel.push(newButton);
cmp.set("v.secondPanel", secondPanel);
);
,
handlePress: function(component, event, helper)
)
Now, if what you need is a dynamically determined number of dynamic component slots in something like an iteration, that might be a situation that calls for decomposing this component into a suite of more elemental components (which themselves might or might not contain facets) rather than building it all into a single massive component, or following the example (again in the linked documentation) that dynamically instantiates children of dynamically instantiated components.
That said, in most cases it seems to be better design to decompose components and conditionally render rather than using very deep dynamic instantiation.
answered Sep 9 at 18:44
David Reed
19.7k21540
Decomposition works fine. Thank you.
– hellohowdoyoudo
Sep 9 at 19:41
add a comment |Â
up vote
9
down vote
accepted
A Lightning attribute like v.body, which is typed as Aura.Component, is called a facet. It's perfectly legal to have multiple facets in your component.
You'd have to do something more like this, if I may modify your example component to suit. Note the Aura.Component-typed attributes: these behave like v.body in that they hold dynamically-instantiated Lightning components, but you can place them as you please and have more than one as needed.
<aura:component>
<aura:attribute type="Aura.Component" name="firstPanel" />
<aura:attribute type="Aura.Component" name="secondPanel" />
<aura:handler name="init" value="! this " action="! c.doInit " />
<div class="wasCreatedDynamicallyInCode">
Here should go the first component:
<div id="addALightningComponentHere1">
! v.firstPanel
</div>
</div>
<div class="wasCreatedDynamicallyInCode">
Here should go the second component:
<div id="addALightningComponentHere2">
! v.secondPanel
</div>
</div>
</aura:component>
Then, in your JavaScript controller, you'd do something like the below (adapted from the linked documentation, and omitting error handling and action handler body for clarity):
(
doInit : function(cmp)
$A.createComponent(
"lightning:button",
"aura:id": "findableAuraId",
"label": "Press Me First",
"onclick": cmp.getReference("c.handlePress")
,
function(newButton, status, errorMessage)
//Add the new button to the body array
if (status === "SUCCESS")
var firstPanel = cmp.get("v.firstPanel");
firstPanel.push(newButton);
cmp.set("v.firstPanel", firstPanel);
);
$A.createComponent(
"lightning:button",
"aura:id": "findableAuraId",
"label": "Press Me Second",
"onclick": cmp.getReference("c.handlePress")
,
function(newButton, status, errorMessage)
//Add the new button to the body array
if (status === "SUCCESS")
var secondPanel = cmp.get("v.secondPanel");
secondPanel.push(newButton);
cmp.set("v.secondPanel", secondPanel);
);
,
handlePress: function(component, event, helper)
)
Now, if what you need is a dynamically determined number of dynamic component slots in something like an iteration, that might be a situation that calls for decomposing this component into a suite of more elemental components (which themselves might or might not contain facets) rather than building it all into a single massive component, or following the example (again in the linked documentation) that dynamically instantiates children of dynamically instantiated components.
That said, in most cases it seems to be better design to decompose components and conditionally render rather than using very deep dynamic instantiation.
answered Sep 9 at 18:44
David Reed
19.7k21540
Decomposition works fine. Thank you.
– hellohowdoyoudo
Sep 9 at 19:41
add a comment |Â
up vote
9
down vote
accepted
up vote
9
down vote
accepted
A Lightning attribute like v.body, which is typed as Aura.Component, is called a facet. It's perfectly legal to have multiple facets in your component.
You'd have to do something more like this, if I may modify your example component to suit. Note the Aura.Component-typed attributes: these behave like v.body in that they hold dynamically-instantiated Lightning components, but you can place them as you please and have more than one as needed.
<aura:component>
<aura:attribute type="Aura.Component" name="firstPanel" />
<aura:attribute type="Aura.Component" name="secondPanel" />
<aura:handler name="init" value="! this " action="! c.doInit " />
<div class="wasCreatedDynamicallyInCode">
Here should go the first component:
<div id="addALightningComponentHere1">
! v.firstPanel
</div>
</div>
<div class="wasCreatedDynamicallyInCode">
Here should go the second component:
<div id="addALightningComponentHere2">
! v.secondPanel
</div>
</div>
</aura:component>
Then, in your JavaScript controller, you'd do something like the below (adapted from the linked documentation, and omitting error handling and action handler body for clarity):
(
doInit : function(cmp)
$A.createComponent(
"lightning:button",
"aura:id": "findableAuraId",
"label": "Press Me First",
"onclick": cmp.getReference("c.handlePress")
,
function(newButton, status, errorMessage)
//Add the new button to the body array
if (status === "SUCCESS")
var firstPanel = cmp.get("v.firstPanel");
firstPanel.push(newButton);
cmp.set("v.firstPanel", firstPanel);
);
$A.createComponent(
"lightning:button",
"aura:id": "findableAuraId",
"label": "Press Me Second",
"onclick": cmp.getReference("c.handlePress")
,
function(newButton, status, errorMessage)
//Add the new button to the body array
if (status === "SUCCESS")
var secondPanel = cmp.get("v.secondPanel");
secondPanel.push(newButton);
cmp.set("v.secondPanel", secondPanel);
);
,
handlePress: function(component, event, helper)
)
Now, if what you need is a dynamically determined number of dynamic component slots in something like an iteration, that might be a situation that calls for decomposing this component into a suite of more elemental components (which themselves might or might not contain facets) rather than building it all into a single massive component, or following the example (again in the linked documentation) that dynamically instantiates children of dynamically instantiated components.
That said, in most cases it seems to be better design to decompose components and conditionally render rather than using very deep dynamic instantiation.
answered Sep 9 at 18:44
David Reed
19.7k21540
A Lightning attribute like v.body, which is typed as Aura.Component, is called a facet. It's perfectly legal to have multiple facets in your component.
You'd have to do something more like this, if I may modify your example component to suit. Note the Aura.Component-typed attributes: these behave like v.body in that they hold dynamically-instantiated Lightning components, but you can place them as you please and have more than one as needed.
<aura:component>
<aura:attribute type="Aura.Component" name="firstPanel" />
<aura:attribute type="Aura.Component" name="secondPanel" />
<aura:handler name="init" value="! this " action="! c.doInit " />
<div class="wasCreatedDynamicallyInCode">
Here should go the first component:
<div id="addALightningComponentHere1">
! v.firstPanel
</div>
</div>
<div class="wasCreatedDynamicallyInCode">
Here should go the second component:
<div id="addALightningComponentHere2">
! v.secondPanel
</div>
</div>
</aura:component>
Then, in your JavaScript controller, you'd do something like the below (adapted from the linked documentation, and omitting error handling and action handler body for clarity):
(
doInit : function(cmp)
$A.createComponent(
"lightning:button",
"aura:id": "findableAuraId",
"label": "Press Me First",
"onclick": cmp.getReference("c.handlePress")
,
function(newButton, status, errorMessage)
//Add the new button to the body array
if (status === "SUCCESS")
var firstPanel = cmp.get("v.firstPanel");
firstPanel.push(newButton);
cmp.set("v.firstPanel", firstPanel);
);
$A.createComponent(
"lightning:button",
"aura:id": "findableAuraId",
"label": "Press Me Second",
"onclick": cmp.getReference("c.handlePress")
,
function(newButton, status, errorMessage)
//Add the new button to the body array
if (status === "SUCCESS")
var secondPanel = cmp.get("v.secondPanel");
secondPanel.push(newButton);
cmp.set("v.secondPanel", secondPanel);
);
,
handlePress: function(component, event, helper)
)
Now, if what you need is a dynamically determined number of dynamic component slots in something like an iteration, that might be a situation that calls for decomposing this component into a suite of more elemental components (which themselves might or might not contain facets) rather than building it all into a single massive component, or following the example (again in the linked documentation) that dynamically instantiates children of dynamically instantiated components.
That said, in most cases it seems to be better design to decompose components and conditionally render rather than using very deep dynamic instantiation.
answered Sep 9 at 18:44
David Reed
19.7k21540
edited 2 days ago
answered Sep 9 at 18:44
David Reed
19.7k21540
answered Sep 9 at 18:44
David Reed
19.7k21540
answered Sep 9 at 18:44
David Reed
19.7k21540
19.7k21540
Decomposition works fine. Thank you.
– hellohowdoyoudo
Sep 9 at 19:41
add a comment |Â
Decomposition works fine. Thank you.
– hellohowdoyoudo
Sep 9 at 19:41
Decomposition works fine. Thank you.
– hellohowdoyoudo
Sep 9 at 19:41
Decomposition works fine. Thank you.
– hellohowdoyoudo
Sep 9 at 19:41
add a comment |Â
hellohowdoyoudo is a new contributor. Be nice, and check out our Code of Conduct.
hellohowdoyoudo is a new contributor. Be nice, and check out our Code of Conduct.
hellohowdoyoudo is a new contributor. Be nice, and check out our Code of Conduct.
hellohowdoyoudo is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f231778%2fdynamically-create-a-lightning-component-and-put-it-into-a-custom-lightning-comp%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Yes it is and the link you have included includes the relevant material. Where are you stuck?
– Keith C
Sep 9 at 17:36
@KeithC, could you, please, provide a JavaScript code to accomplish this? Since I can follow only examples in documentation and do not know how to add the component without having a
!v.body.– hellohowdoyoudo
Sep 9 at 17:37
What is stopping you adding a
!v.body?– Keith C
Sep 9 at 17:39
@KeithC, I can have multiple places in my custom lightning component where I would like to add another lightning component. Let me update the question to elaborate this.
– hellohowdoyoudo
Sep 9 at 17:49
You're allowed to have more than one facet (attribute of type
Aura.Component), beyond justv.body.– David Reed
Sep 9 at 17:59