Lightning Web Components - Not available in app builder2019 Community Moderator Electiondesign:attribute on Locked Developer Controlled Package upgradeWhat are Lightning Web ComponentsLightning web components issue with SFDX push and pullLightning Web Component available in Community BuilderLightning Web Components Easy Spaces sample application LWC component codeNot being able to access previous Developer Edition Account after creating and logging in to the new pre-release editionSLDS classes on (new) base Lightning web components don't workHow to delete a Lightning Web Component?Lightning Web Component error : afterRender threw an error in 'c:bearList' [e[Ei] is not a function]Error when adding different Lightning Web Components to the Playground
What to do with wrong results in talks?
Is exact Kanji stroke length important?
How to be diplomatic in refusing to write code that breaches the privacy of our users
Is this Spell Mimic feat balanced?
Is there a problem with hiding "forgot password" until it's needed?
Valid Badminton Score?
What are the ramifications of creating a homebrew world without an Astral Plane?
How do I keep an essay about "feeling flat" from feeling flat?
Efficiently merge handle parallel feature branches in SFDX
Time travel short story where a man arrives in the late 19th century in a time machine and then sends the machine back into the past
Applicability of Single Responsibility Principle
Coordinate position not precise
Are there any comparative studies done between Ashtavakra Gita and Buddhim?
I'm in charge of equipment buying but no one's ever happy with what I choose. How to fix this?
How does residential electricity work?
Your magic is very sketchy
Do there exist finite commutative rings with identity that are not Bézout rings?
Is there any easy technique written in Bhagavad GITA to control lust?
The baby cries all morning
Teaching indefinite integrals that require special-casing
Using parameter substitution on a Bash array
If you attempt to grapple an opponent that you are hidden from, do they roll at disadvantage?
Why "be dealt cards" rather than "be dealing cards"?
Why is delta-v is the most useful quantity for planning space travel?
Lightning Web Components - Not available in app builder
2019 Community Moderator Electiondesign:attribute on Locked Developer Controlled Package upgradeWhat are Lightning Web ComponentsLightning web components issue with SFDX push and pullLightning Web Component available in Community BuilderLightning Web Components Easy Spaces sample application LWC component codeNot being able to access previous Developer Edition Account after creating and logging in to the new pre-release editionSLDS classes on (new) base Lightning web components don't workHow to delete a Lightning Web Component?Lightning Web Component error : afterRender threw an error in 'c:bearList' [e[Ei] is not a function]Error when adding different Lightning Web Components to the Playground
I'm developing a lightning web component with org based development and I'm finding that the component isn't available in the app builder, despite (as far as I can tell) making it available in the component definition. I've attempted this with a my own component and also directly copying the "HelloWorld" Lightning component in this trailhead:
Create a Hello World Lightning Web Component
My component is pretty simple, and I'd like it to be available on the Contact record page. Here is the config on that component:
<?xml version="1.0" encoding="UTF-8"?>
<LightningComponentBundle xmlns="http://soap.sforce.com/2006/04/metadata" fqn="contact_CRSProfileLayout">
<apiVersion>45.0</apiVersion>
<description>Use this component to display the fields from this person's related CRS Profile</description>
<masterLabel>CRS Profile</masterLabel>
<isExposed>true</isExposed>
<targets>
<target>lightning__RecordPage</target>
</targets>
<targetConfigs>
<targetConfig targets="lightning__RecordPage">
<objects>
<object>Contact</object>
</objects>
</targetConfig>
</targetConfigs>
</LightningComponentBundle>
I've deployed the components into my sandbox from Visual Studio Code using the "SFDX: Deploy Source to Org" command and I can see that the lighting web components are in the sandbox when I navigate to them in the admin interface (I can't confirm that they exactly match what I'm seeing in Source, but I can see the timestamp of their update is correct).
However, neither of them are appearing in the ap builder. I would expect both to appear on a record page app builder and the hellowWorld component only to appear on a home page Lightning Page.
Are there general troubleshooting steps I should be taking?
salesforcedx lightning-web-components
add a comment |
I'm developing a lightning web component with org based development and I'm finding that the component isn't available in the app builder, despite (as far as I can tell) making it available in the component definition. I've attempted this with a my own component and also directly copying the "HelloWorld" Lightning component in this trailhead:
Create a Hello World Lightning Web Component
My component is pretty simple, and I'd like it to be available on the Contact record page. Here is the config on that component:
<?xml version="1.0" encoding="UTF-8"?>
<LightningComponentBundle xmlns="http://soap.sforce.com/2006/04/metadata" fqn="contact_CRSProfileLayout">
<apiVersion>45.0</apiVersion>
<description>Use this component to display the fields from this person's related CRS Profile</description>
<masterLabel>CRS Profile</masterLabel>
<isExposed>true</isExposed>
<targets>
<target>lightning__RecordPage</target>
</targets>
<targetConfigs>
<targetConfig targets="lightning__RecordPage">
<objects>
<object>Contact</object>
</objects>
</targetConfig>
</targetConfigs>
</LightningComponentBundle>
I've deployed the components into my sandbox from Visual Studio Code using the "SFDX: Deploy Source to Org" command and I can see that the lighting web components are in the sandbox when I navigate to them in the admin interface (I can't confirm that they exactly match what I'm seeing in Source, but I can see the timestamp of their update is correct).
However, neither of them are appearing in the ap builder. I would expect both to appear on a record page app builder and the hellowWorld component only to appear on a home page Lightning Page.
Are there general troubleshooting steps I should be taking?
salesforcedx lightning-web-components
add a comment |
I'm developing a lightning web component with org based development and I'm finding that the component isn't available in the app builder, despite (as far as I can tell) making it available in the component definition. I've attempted this with a my own component and also directly copying the "HelloWorld" Lightning component in this trailhead:
Create a Hello World Lightning Web Component
My component is pretty simple, and I'd like it to be available on the Contact record page. Here is the config on that component:
<?xml version="1.0" encoding="UTF-8"?>
<LightningComponentBundle xmlns="http://soap.sforce.com/2006/04/metadata" fqn="contact_CRSProfileLayout">
<apiVersion>45.0</apiVersion>
<description>Use this component to display the fields from this person's related CRS Profile</description>
<masterLabel>CRS Profile</masterLabel>
<isExposed>true</isExposed>
<targets>
<target>lightning__RecordPage</target>
</targets>
<targetConfigs>
<targetConfig targets="lightning__RecordPage">
<objects>
<object>Contact</object>
</objects>
</targetConfig>
</targetConfigs>
</LightningComponentBundle>
I've deployed the components into my sandbox from Visual Studio Code using the "SFDX: Deploy Source to Org" command and I can see that the lighting web components are in the sandbox when I navigate to them in the admin interface (I can't confirm that they exactly match what I'm seeing in Source, but I can see the timestamp of their update is correct).
However, neither of them are appearing in the ap builder. I would expect both to appear on a record page app builder and the hellowWorld component only to appear on a home page Lightning Page.
Are there general troubleshooting steps I should be taking?
salesforcedx lightning-web-components
I'm developing a lightning web component with org based development and I'm finding that the component isn't available in the app builder, despite (as far as I can tell) making it available in the component definition. I've attempted this with a my own component and also directly copying the "HelloWorld" Lightning component in this trailhead:
Create a Hello World Lightning Web Component
My component is pretty simple, and I'd like it to be available on the Contact record page. Here is the config on that component:
<?xml version="1.0" encoding="UTF-8"?>
<LightningComponentBundle xmlns="http://soap.sforce.com/2006/04/metadata" fqn="contact_CRSProfileLayout">
<apiVersion>45.0</apiVersion>
<description>Use this component to display the fields from this person's related CRS Profile</description>
<masterLabel>CRS Profile</masterLabel>
<isExposed>true</isExposed>
<targets>
<target>lightning__RecordPage</target>
</targets>
<targetConfigs>
<targetConfig targets="lightning__RecordPage">
<objects>
<object>Contact</object>
</objects>
</targetConfig>
</targetConfigs>
</LightningComponentBundle>
I've deployed the components into my sandbox from Visual Studio Code using the "SFDX: Deploy Source to Org" command and I can see that the lighting web components are in the sandbox when I navigate to them in the admin interface (I can't confirm that they exactly match what I'm seeing in Source, but I can see the timestamp of their update is correct).
However, neither of them are appearing in the ap builder. I would expect both to appear on a record page app builder and the hellowWorld component only to appear on a home page Lightning Page.
Are there general troubleshooting steps I should be taking?
salesforcedx lightning-web-components
salesforcedx lightning-web-components
edited yesterday
Marcell Csiszár
33
33
asked yesterday
BigearsBigears
393122
393122
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
You currently have the isExposed
attribute set to false
, it needs to be set to true
for the component to be available on the targeted pages and app builder.
<isExposed>true</isExposed>
By definition:
isExposed
A Boolean value. Exposes the component in all orgs, and in Lightning App Builder and Community Builder
Unfortunately, I'd already tried that (and the helloWorld component was set to Exposed = true. Unfortunately, this hasn't made any difference. I've made the change in the original question so it's clearer.
– Bigears
yesterday
Did you redeploy the configuration file after making the change?
– Jayant Das
yesterday
Thank you for checking, but yes - I'm clicking "SFDX: deploy Source to Org" after every change, just to see.
– Bigears
yesterday
You have few different components mentioned in your question and that your original question was updated. I will recommend to start with one of the components say hello world and try to update the attribute and see if that works. There’s no other attribute which makes the component available in app builder.
– Jayant Das
yesterday
Additionally just to make sure that the deployment was successful, check for messageended with exit code 0
to make sure the deployment was indeed successful.
– Jayant Das
yesterday
|
show 3 more comments
The issue wasn't the deploy, it was me - I'm inexperienced with Visual Studio Code.
I wasn't following the correct order of actions. The local save wasn't happening, so I was repeatedly deploying a "blank" component to the server.
I've ensured that the local save is happening and the components are now showing up as expected.
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "459"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
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
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f255160%2flightning-web-components-not-available-in-app-builder%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
You currently have the isExposed
attribute set to false
, it needs to be set to true
for the component to be available on the targeted pages and app builder.
<isExposed>true</isExposed>
By definition:
isExposed
A Boolean value. Exposes the component in all orgs, and in Lightning App Builder and Community Builder
Unfortunately, I'd already tried that (and the helloWorld component was set to Exposed = true. Unfortunately, this hasn't made any difference. I've made the change in the original question so it's clearer.
– Bigears
yesterday
Did you redeploy the configuration file after making the change?
– Jayant Das
yesterday
Thank you for checking, but yes - I'm clicking "SFDX: deploy Source to Org" after every change, just to see.
– Bigears
yesterday
You have few different components mentioned in your question and that your original question was updated. I will recommend to start with one of the components say hello world and try to update the attribute and see if that works. There’s no other attribute which makes the component available in app builder.
– Jayant Das
yesterday
Additionally just to make sure that the deployment was successful, check for messageended with exit code 0
to make sure the deployment was indeed successful.
– Jayant Das
yesterday
|
show 3 more comments
You currently have the isExposed
attribute set to false
, it needs to be set to true
for the component to be available on the targeted pages and app builder.
<isExposed>true</isExposed>
By definition:
isExposed
A Boolean value. Exposes the component in all orgs, and in Lightning App Builder and Community Builder
Unfortunately, I'd already tried that (and the helloWorld component was set to Exposed = true. Unfortunately, this hasn't made any difference. I've made the change in the original question so it's clearer.
– Bigears
yesterday
Did you redeploy the configuration file after making the change?
– Jayant Das
yesterday
Thank you for checking, but yes - I'm clicking "SFDX: deploy Source to Org" after every change, just to see.
– Bigears
yesterday
You have few different components mentioned in your question and that your original question was updated. I will recommend to start with one of the components say hello world and try to update the attribute and see if that works. There’s no other attribute which makes the component available in app builder.
– Jayant Das
yesterday
Additionally just to make sure that the deployment was successful, check for messageended with exit code 0
to make sure the deployment was indeed successful.
– Jayant Das
yesterday
|
show 3 more comments
You currently have the isExposed
attribute set to false
, it needs to be set to true
for the component to be available on the targeted pages and app builder.
<isExposed>true</isExposed>
By definition:
isExposed
A Boolean value. Exposes the component in all orgs, and in Lightning App Builder and Community Builder
You currently have the isExposed
attribute set to false
, it needs to be set to true
for the component to be available on the targeted pages and app builder.
<isExposed>true</isExposed>
By definition:
isExposed
A Boolean value. Exposes the component in all orgs, and in Lightning App Builder and Community Builder
edited yesterday
answered yesterday
Jayant DasJayant Das
17.2k21330
17.2k21330
Unfortunately, I'd already tried that (and the helloWorld component was set to Exposed = true. Unfortunately, this hasn't made any difference. I've made the change in the original question so it's clearer.
– Bigears
yesterday
Did you redeploy the configuration file after making the change?
– Jayant Das
yesterday
Thank you for checking, but yes - I'm clicking "SFDX: deploy Source to Org" after every change, just to see.
– Bigears
yesterday
You have few different components mentioned in your question and that your original question was updated. I will recommend to start with one of the components say hello world and try to update the attribute and see if that works. There’s no other attribute which makes the component available in app builder.
– Jayant Das
yesterday
Additionally just to make sure that the deployment was successful, check for messageended with exit code 0
to make sure the deployment was indeed successful.
– Jayant Das
yesterday
|
show 3 more comments
Unfortunately, I'd already tried that (and the helloWorld component was set to Exposed = true. Unfortunately, this hasn't made any difference. I've made the change in the original question so it's clearer.
– Bigears
yesterday
Did you redeploy the configuration file after making the change?
– Jayant Das
yesterday
Thank you for checking, but yes - I'm clicking "SFDX: deploy Source to Org" after every change, just to see.
– Bigears
yesterday
You have few different components mentioned in your question and that your original question was updated. I will recommend to start with one of the components say hello world and try to update the attribute and see if that works. There’s no other attribute which makes the component available in app builder.
– Jayant Das
yesterday
Additionally just to make sure that the deployment was successful, check for messageended with exit code 0
to make sure the deployment was indeed successful.
– Jayant Das
yesterday
Unfortunately, I'd already tried that (and the helloWorld component was set to Exposed = true. Unfortunately, this hasn't made any difference. I've made the change in the original question so it's clearer.
– Bigears
yesterday
Unfortunately, I'd already tried that (and the helloWorld component was set to Exposed = true. Unfortunately, this hasn't made any difference. I've made the change in the original question so it's clearer.
– Bigears
yesterday
Did you redeploy the configuration file after making the change?
– Jayant Das
yesterday
Did you redeploy the configuration file after making the change?
– Jayant Das
yesterday
Thank you for checking, but yes - I'm clicking "SFDX: deploy Source to Org" after every change, just to see.
– Bigears
yesterday
Thank you for checking, but yes - I'm clicking "SFDX: deploy Source to Org" after every change, just to see.
– Bigears
yesterday
You have few different components mentioned in your question and that your original question was updated. I will recommend to start with one of the components say hello world and try to update the attribute and see if that works. There’s no other attribute which makes the component available in app builder.
– Jayant Das
yesterday
You have few different components mentioned in your question and that your original question was updated. I will recommend to start with one of the components say hello world and try to update the attribute and see if that works. There’s no other attribute which makes the component available in app builder.
– Jayant Das
yesterday
Additionally just to make sure that the deployment was successful, check for message
ended with exit code 0
to make sure the deployment was indeed successful.– Jayant Das
yesterday
Additionally just to make sure that the deployment was successful, check for message
ended with exit code 0
to make sure the deployment was indeed successful.– Jayant Das
yesterday
|
show 3 more comments
The issue wasn't the deploy, it was me - I'm inexperienced with Visual Studio Code.
I wasn't following the correct order of actions. The local save wasn't happening, so I was repeatedly deploying a "blank" component to the server.
I've ensured that the local save is happening and the components are now showing up as expected.
add a comment |
The issue wasn't the deploy, it was me - I'm inexperienced with Visual Studio Code.
I wasn't following the correct order of actions. The local save wasn't happening, so I was repeatedly deploying a "blank" component to the server.
I've ensured that the local save is happening and the components are now showing up as expected.
add a comment |
The issue wasn't the deploy, it was me - I'm inexperienced with Visual Studio Code.
I wasn't following the correct order of actions. The local save wasn't happening, so I was repeatedly deploying a "blank" component to the server.
I've ensured that the local save is happening and the components are now showing up as expected.
The issue wasn't the deploy, it was me - I'm inexperienced with Visual Studio Code.
I wasn't following the correct order of actions. The local save wasn't happening, so I was repeatedly deploying a "blank" component to the server.
I've ensured that the local save is happening and the components are now showing up as expected.
answered yesterday
BigearsBigears
393122
393122
add a comment |
add a comment |
Thanks for contributing an answer to Salesforce Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f255160%2flightning-web-components-not-available-in-app-builder%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown