Magento2 : Change custom attribute scope not working












1















I create a product custom attribute programatically. The scope was WEBSITE. But now I just realised that this attribute must have the scope as STORE, because I need different values according to the store view.



I changed the scope in backend, clean the cache, and when I went to edit the product, the scope was correct [STORE]. Then I change store, view so I can insert the value for the store view and the scope changed to [WEBSITE].



I went back and the scope was wrong again [WEBSITE].



I went again to the attribute (Stores > Attributes > Product), choose my attribute, and the attribute had the right scope. I didn't change anything, only save the attribute again and clean the cache. Then I edit the product and the scope was correct [STORE], then I change store view and the scope was wrong again [WEBSITE].



I check database and the attribute is ok.



Did this happening to anyone?
Anyone has a clue about this?



Thank you










share|improve this question
















bumped to the homepage by Community 9 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.




















    1















    I create a product custom attribute programatically. The scope was WEBSITE. But now I just realised that this attribute must have the scope as STORE, because I need different values according to the store view.



    I changed the scope in backend, clean the cache, and when I went to edit the product, the scope was correct [STORE]. Then I change store, view so I can insert the value for the store view and the scope changed to [WEBSITE].



    I went back and the scope was wrong again [WEBSITE].



    I went again to the attribute (Stores > Attributes > Product), choose my attribute, and the attribute had the right scope. I didn't change anything, only save the attribute again and clean the cache. Then I edit the product and the scope was correct [STORE], then I change store view and the scope was wrong again [WEBSITE].



    I check database and the attribute is ok.



    Did this happening to anyone?
    Anyone has a clue about this?



    Thank you










    share|improve this question
















    bumped to the homepage by Community 9 mins ago


    This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.


















      1












      1








      1








      I create a product custom attribute programatically. The scope was WEBSITE. But now I just realised that this attribute must have the scope as STORE, because I need different values according to the store view.



      I changed the scope in backend, clean the cache, and when I went to edit the product, the scope was correct [STORE]. Then I change store, view so I can insert the value for the store view and the scope changed to [WEBSITE].



      I went back and the scope was wrong again [WEBSITE].



      I went again to the attribute (Stores > Attributes > Product), choose my attribute, and the attribute had the right scope. I didn't change anything, only save the attribute again and clean the cache. Then I edit the product and the scope was correct [STORE], then I change store view and the scope was wrong again [WEBSITE].



      I check database and the attribute is ok.



      Did this happening to anyone?
      Anyone has a clue about this?



      Thank you










      share|improve this question
















      I create a product custom attribute programatically. The scope was WEBSITE. But now I just realised that this attribute must have the scope as STORE, because I need different values according to the store view.



      I changed the scope in backend, clean the cache, and when I went to edit the product, the scope was correct [STORE]. Then I change store, view so I can insert the value for the store view and the scope changed to [WEBSITE].



      I went back and the scope was wrong again [WEBSITE].



      I went again to the attribute (Stores > Attributes > Product), choose my attribute, and the attribute had the right scope. I didn't change anything, only save the attribute again and clean the cache. Then I edit the product and the scope was correct [STORE], then I change store view and the scope was wrong again [WEBSITE].



      I check database and the attribute is ok.



      Did this happening to anyone?
      Anyone has a clue about this?



      Thank you







      magento2 product-attribute scope






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Dec 14 '17 at 13:21









      Sarfaraj

      378318




      378318










      asked Dec 14 '17 at 12:11









      mvistasmvistas

      1616




      1616





      bumped to the homepage by Community 9 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







      bumped to the homepage by Community 9 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
























          2 Answers
          2






          active

          oldest

          votes


















          0














          Try to run this command:



          bin/magento indexer:reindex

          bin/magento setup:static-content:deploy





          share|improve this answer
























          • I did this already and didn't solve the issue. thank you

            – mvistas
            Dec 14 '17 at 12:23



















          0














          You've probably solved your problem, but here is solution for people coming here from google as me. I've managed it by editing it straight in database.



          It's not recommended to do such things - the safest way is to delete this attribute and add it again, but sometimes you have no choice. This is e.g. how to change attribute scope to GLOBAL.



          UPDATE catalog_eav_attribute SET is_global = 1, apply_to = 'simple,virtual,configurable' WHERE attribute_id = YOUR_ATTRIBUTE_ID;


          And then refresh cache.






          share|improve this answer























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "479"
            };
            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%2fmagento.stackexchange.com%2fquestions%2f205810%2fmagento2-change-custom-attribute-scope-not-working%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









            0














            Try to run this command:



            bin/magento indexer:reindex

            bin/magento setup:static-content:deploy





            share|improve this answer
























            • I did this already and didn't solve the issue. thank you

              – mvistas
              Dec 14 '17 at 12:23
















            0














            Try to run this command:



            bin/magento indexer:reindex

            bin/magento setup:static-content:deploy





            share|improve this answer
























            • I did this already and didn't solve the issue. thank you

              – mvistas
              Dec 14 '17 at 12:23














            0












            0








            0







            Try to run this command:



            bin/magento indexer:reindex

            bin/magento setup:static-content:deploy





            share|improve this answer













            Try to run this command:



            bin/magento indexer:reindex

            bin/magento setup:static-content:deploy






            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Dec 14 '17 at 12:18









            Nero PhungNero Phung

            8191420




            8191420













            • I did this already and didn't solve the issue. thank you

              – mvistas
              Dec 14 '17 at 12:23



















            • I did this already and didn't solve the issue. thank you

              – mvistas
              Dec 14 '17 at 12:23

















            I did this already and didn't solve the issue. thank you

            – mvistas
            Dec 14 '17 at 12:23





            I did this already and didn't solve the issue. thank you

            – mvistas
            Dec 14 '17 at 12:23













            0














            You've probably solved your problem, but here is solution for people coming here from google as me. I've managed it by editing it straight in database.



            It's not recommended to do such things - the safest way is to delete this attribute and add it again, but sometimes you have no choice. This is e.g. how to change attribute scope to GLOBAL.



            UPDATE catalog_eav_attribute SET is_global = 1, apply_to = 'simple,virtual,configurable' WHERE attribute_id = YOUR_ATTRIBUTE_ID;


            And then refresh cache.






            share|improve this answer




























              0














              You've probably solved your problem, but here is solution for people coming here from google as me. I've managed it by editing it straight in database.



              It's not recommended to do such things - the safest way is to delete this attribute and add it again, but sometimes you have no choice. This is e.g. how to change attribute scope to GLOBAL.



              UPDATE catalog_eav_attribute SET is_global = 1, apply_to = 'simple,virtual,configurable' WHERE attribute_id = YOUR_ATTRIBUTE_ID;


              And then refresh cache.






              share|improve this answer


























                0












                0








                0







                You've probably solved your problem, but here is solution for people coming here from google as me. I've managed it by editing it straight in database.



                It's not recommended to do such things - the safest way is to delete this attribute and add it again, but sometimes you have no choice. This is e.g. how to change attribute scope to GLOBAL.



                UPDATE catalog_eav_attribute SET is_global = 1, apply_to = 'simple,virtual,configurable' WHERE attribute_id = YOUR_ATTRIBUTE_ID;


                And then refresh cache.






                share|improve this answer













                You've probably solved your problem, but here is solution for people coming here from google as me. I've managed it by editing it straight in database.



                It's not recommended to do such things - the safest way is to delete this attribute and add it again, but sometimes you have no choice. This is e.g. how to change attribute scope to GLOBAL.



                UPDATE catalog_eav_attribute SET is_global = 1, apply_to = 'simple,virtual,configurable' WHERE attribute_id = YOUR_ATTRIBUTE_ID;


                And then refresh cache.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Mar 14 '18 at 21:58









                A.MaksymiukA.Maksymiuk

                413512




                413512






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Magento 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%2fmagento.stackexchange.com%2fquestions%2f205810%2fmagento2-change-custom-attribute-scope-not-working%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

                    Magento 2 controller redirect on button click in phtml file

                    Polycentropodidae