Lightning Web Components - Not available in app builder





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







1















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).



Successful deployment



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.



enter image description here



Are there general troubleshooting steps I should be taking?










share|improve this question































    1















    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).



    Successful deployment



    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.



    enter image description here



    Are there general troubleshooting steps I should be taking?










    share|improve this question



























      1












      1








      1








      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).



      Successful deployment



      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.



      enter image description here



      Are there general troubleshooting steps I should be taking?










      share|improve this question
















      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).



      Successful deployment



      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.



      enter image description here



      Are there general troubleshooting steps I should be taking?







      salesforcedx lightning-web-components






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Mar 25 at 19:03









      Marcell Csiszár

      1448




      1448










      asked Mar 25 at 12:28









      BigearsBigears

      393122




      393122






















          2 Answers
          2






          active

          oldest

          votes


















          6














          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







          share|improve this answer


























          • 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
            Mar 25 at 12:46











          • Did you redeploy the configuration file after making the change?

            – Jayant Das
            Mar 25 at 12:49











          • Thank you for checking, but yes - I'm clicking "SFDX: deploy Source to Org" after every change, just to see.

            – Bigears
            Mar 25 at 12:53











          • 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
            Mar 25 at 12:59











          • 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
            Mar 25 at 13:04



















          1














          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.






          share|improve this answer
























            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
            });


            }
            });














            draft saved

            draft discarded


















            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









            6














            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







            share|improve this answer


























            • 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
              Mar 25 at 12:46











            • Did you redeploy the configuration file after making the change?

              – Jayant Das
              Mar 25 at 12:49











            • Thank you for checking, but yes - I'm clicking "SFDX: deploy Source to Org" after every change, just to see.

              – Bigears
              Mar 25 at 12:53











            • 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
              Mar 25 at 12:59











            • 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
              Mar 25 at 13:04
















            6














            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







            share|improve this answer


























            • 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
              Mar 25 at 12:46











            • Did you redeploy the configuration file after making the change?

              – Jayant Das
              Mar 25 at 12:49











            • Thank you for checking, but yes - I'm clicking "SFDX: deploy Source to Org" after every change, just to see.

              – Bigears
              Mar 25 at 12:53











            • 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
              Mar 25 at 12:59











            • 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
              Mar 25 at 13:04














            6












            6








            6







            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







            share|improve this answer















            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








            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited Mar 25 at 12:37

























            answered Mar 25 at 12:32









            Jayant DasJayant Das

            17.8k21330




            17.8k21330













            • 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
              Mar 25 at 12:46











            • Did you redeploy the configuration file after making the change?

              – Jayant Das
              Mar 25 at 12:49











            • Thank you for checking, but yes - I'm clicking "SFDX: deploy Source to Org" after every change, just to see.

              – Bigears
              Mar 25 at 12:53











            • 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
              Mar 25 at 12:59











            • 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
              Mar 25 at 13:04



















            • 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
              Mar 25 at 12:46











            • Did you redeploy the configuration file after making the change?

              – Jayant Das
              Mar 25 at 12:49











            • Thank you for checking, but yes - I'm clicking "SFDX: deploy Source to Org" after every change, just to see.

              – Bigears
              Mar 25 at 12:53











            • 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
              Mar 25 at 12:59











            • 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
              Mar 25 at 13:04

















            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
            Mar 25 at 12:46





            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
            Mar 25 at 12:46













            Did you redeploy the configuration file after making the change?

            – Jayant Das
            Mar 25 at 12:49





            Did you redeploy the configuration file after making the change?

            – Jayant Das
            Mar 25 at 12:49













            Thank you for checking, but yes - I'm clicking "SFDX: deploy Source to Org" after every change, just to see.

            – Bigears
            Mar 25 at 12:53





            Thank you for checking, but yes - I'm clicking "SFDX: deploy Source to Org" after every change, just to see.

            – Bigears
            Mar 25 at 12:53













            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
            Mar 25 at 12:59





            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
            Mar 25 at 12:59













            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
            Mar 25 at 13:04





            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
            Mar 25 at 13:04













            1














            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.






            share|improve this answer




























              1














              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.






              share|improve this answer


























                1












                1








                1







                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.






                share|improve this answer













                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.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Mar 25 at 13:26









                BigearsBigears

                393122




                393122






























                    draft saved

                    draft discarded




















































                    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.




                    draft saved


                    draft discarded














                    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





















































                    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







                    Popular posts from this blog

                    "Incorrect syntax near the keyword 'ON'. (on update cascade, on delete cascade,)

                    Alcedinidae

                    RAC Tourist Trophy