Attribute not shown in layer navigation












1














I migrated from Magento 1.9.3.3 to Magento 2.1.7 EE. I have one issue, that is some of the attributes(multiple select) not shown in layer navigation.



Create new category called test,
Assign two products to test category, that two products have multiple select attributes.



Multiple select attribute have the below propertiesenter image description here



but it is not rendering in layer navigation.



If anyone faces this issue before, please post the solution.



Note: Migrated attributes only have this issues, If I create a new attribute with similar fashion, it works!










share|improve this question
























  • did you ever figure out the issue, i have the same problem in 2.2.2, just like you mention, only on "multiple select" attributes migrated... I suspect some field or mapping is missing...
    – iphigenie
    Jan 10 '18 at 16:56












  • @iphigenie see my answer. I hope it helps!
    – Bilal Usean
    Jan 10 '18 at 17:09
















1














I migrated from Magento 1.9.3.3 to Magento 2.1.7 EE. I have one issue, that is some of the attributes(multiple select) not shown in layer navigation.



Create new category called test,
Assign two products to test category, that two products have multiple select attributes.



Multiple select attribute have the below propertiesenter image description here



but it is not rendering in layer navigation.



If anyone faces this issue before, please post the solution.



Note: Migrated attributes only have this issues, If I create a new attribute with similar fashion, it works!










share|improve this question
























  • did you ever figure out the issue, i have the same problem in 2.2.2, just like you mention, only on "multiple select" attributes migrated... I suspect some field or mapping is missing...
    – iphigenie
    Jan 10 '18 at 16:56












  • @iphigenie see my answer. I hope it helps!
    – Bilal Usean
    Jan 10 '18 at 17:09














1












1








1







I migrated from Magento 1.9.3.3 to Magento 2.1.7 EE. I have one issue, that is some of the attributes(multiple select) not shown in layer navigation.



Create new category called test,
Assign two products to test category, that two products have multiple select attributes.



Multiple select attribute have the below propertiesenter image description here



but it is not rendering in layer navigation.



If anyone faces this issue before, please post the solution.



Note: Migrated attributes only have this issues, If I create a new attribute with similar fashion, it works!










share|improve this question















I migrated from Magento 1.9.3.3 to Magento 2.1.7 EE. I have one issue, that is some of the attributes(multiple select) not shown in layer navigation.



Create new category called test,
Assign two products to test category, that two products have multiple select attributes.



Multiple select attribute have the below propertiesenter image description here



but it is not rendering in layer navigation.



If anyone faces this issue before, please post the solution.



Note: Migrated attributes only have this issues, If I create a new attribute with similar fashion, it works!







magento2 attributes product-attribute layered-navigation






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Sep 7 '17 at 7:52

























asked Sep 7 '17 at 7:26









Bilal Usean

4,44423384




4,44423384












  • did you ever figure out the issue, i have the same problem in 2.2.2, just like you mention, only on "multiple select" attributes migrated... I suspect some field or mapping is missing...
    – iphigenie
    Jan 10 '18 at 16:56












  • @iphigenie see my answer. I hope it helps!
    – Bilal Usean
    Jan 10 '18 at 17:09


















  • did you ever figure out the issue, i have the same problem in 2.2.2, just like you mention, only on "multiple select" attributes migrated... I suspect some field or mapping is missing...
    – iphigenie
    Jan 10 '18 at 16:56












  • @iphigenie see my answer. I hope it helps!
    – Bilal Usean
    Jan 10 '18 at 17:09
















did you ever figure out the issue, i have the same problem in 2.2.2, just like you mention, only on "multiple select" attributes migrated... I suspect some field or mapping is missing...
– iphigenie
Jan 10 '18 at 16:56






did you ever figure out the issue, i have the same problem in 2.2.2, just like you mention, only on "multiple select" attributes migrated... I suspect some field or mapping is missing...
– iphigenie
Jan 10 '18 at 16:56














@iphigenie see my answer. I hope it helps!
– Bilal Usean
Jan 10 '18 at 17:09




@iphigenie see my answer. I hope it helps!
– Bilal Usean
Jan 10 '18 at 17:09










2 Answers
2






active

oldest

votes


















3














In my case migrated multi-select attribute has invalid backend_type value as text, it should be varchar for multiple select



After changing backend_type from text to varchar, it's working.






share|improve this answer





















  • Thanks for the pointer! I can see that this is indeed wrong on my site too. Simply saving the attribute in admin will correct the backend type. Alas that did not move the data itself which is still catalog_product_entity_text when it should be in catalog_product_entity_varchar so I'll check if I can reimport or just do that manually, thankfully it is only 8 attributes.
    – iphigenie
    Jan 11 '18 at 13:01












  • saved my day bro
    – Vinod Kumar
    Jul 3 '18 at 17:52



















0














The steps to resolve this issue after migrating is first to open the attribute and save it again, this will set the type from text to varchar. After this run the SQL below to copy all data from the text to the varchar table.



INSERT IGNORE INTO catalog_product_entity_varchar (store_id, attribute_id, entity_id, value)select store_id, attribute_id, entity_id, value from catalog_product_entity_text where catalog_product_entity_text.attribute_id = {your attribute id} and catalog_product_entity_text.value is not null;


Now delete the data from the text table



DELETE FROM `catalog_product_entity_text` WHERE `attribute_id` = {your attribute id}


Run in terminal




  • php magento2/bin/magento indexer:reindex

  • php magento2/bin/magento cache:flush


If the reindex is giving a duplication error, search for the entity_id in the catalog_product_entity_varchar table and check if there is a duplicate value for the attribute id in the field.






share|improve this answer








New contributor




Dennis van der Graaf is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.


















    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%2f192323%2fattribute-not-shown-in-layer-navigation%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









    3














    In my case migrated multi-select attribute has invalid backend_type value as text, it should be varchar for multiple select



    After changing backend_type from text to varchar, it's working.






    share|improve this answer





















    • Thanks for the pointer! I can see that this is indeed wrong on my site too. Simply saving the attribute in admin will correct the backend type. Alas that did not move the data itself which is still catalog_product_entity_text when it should be in catalog_product_entity_varchar so I'll check if I can reimport or just do that manually, thankfully it is only 8 attributes.
      – iphigenie
      Jan 11 '18 at 13:01












    • saved my day bro
      – Vinod Kumar
      Jul 3 '18 at 17:52
















    3














    In my case migrated multi-select attribute has invalid backend_type value as text, it should be varchar for multiple select



    After changing backend_type from text to varchar, it's working.






    share|improve this answer





















    • Thanks for the pointer! I can see that this is indeed wrong on my site too. Simply saving the attribute in admin will correct the backend type. Alas that did not move the data itself which is still catalog_product_entity_text when it should be in catalog_product_entity_varchar so I'll check if I can reimport or just do that manually, thankfully it is only 8 attributes.
      – iphigenie
      Jan 11 '18 at 13:01












    • saved my day bro
      – Vinod Kumar
      Jul 3 '18 at 17:52














    3












    3








    3






    In my case migrated multi-select attribute has invalid backend_type value as text, it should be varchar for multiple select



    After changing backend_type from text to varchar, it's working.






    share|improve this answer












    In my case migrated multi-select attribute has invalid backend_type value as text, it should be varchar for multiple select



    After changing backend_type from text to varchar, it's working.







    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Jan 10 '18 at 17:08









    Bilal Usean

    4,44423384




    4,44423384












    • Thanks for the pointer! I can see that this is indeed wrong on my site too. Simply saving the attribute in admin will correct the backend type. Alas that did not move the data itself which is still catalog_product_entity_text when it should be in catalog_product_entity_varchar so I'll check if I can reimport or just do that manually, thankfully it is only 8 attributes.
      – iphigenie
      Jan 11 '18 at 13:01












    • saved my day bro
      – Vinod Kumar
      Jul 3 '18 at 17:52


















    • Thanks for the pointer! I can see that this is indeed wrong on my site too. Simply saving the attribute in admin will correct the backend type. Alas that did not move the data itself which is still catalog_product_entity_text when it should be in catalog_product_entity_varchar so I'll check if I can reimport or just do that manually, thankfully it is only 8 attributes.
      – iphigenie
      Jan 11 '18 at 13:01












    • saved my day bro
      – Vinod Kumar
      Jul 3 '18 at 17:52
















    Thanks for the pointer! I can see that this is indeed wrong on my site too. Simply saving the attribute in admin will correct the backend type. Alas that did not move the data itself which is still catalog_product_entity_text when it should be in catalog_product_entity_varchar so I'll check if I can reimport or just do that manually, thankfully it is only 8 attributes.
    – iphigenie
    Jan 11 '18 at 13:01






    Thanks for the pointer! I can see that this is indeed wrong on my site too. Simply saving the attribute in admin will correct the backend type. Alas that did not move the data itself which is still catalog_product_entity_text when it should be in catalog_product_entity_varchar so I'll check if I can reimport or just do that manually, thankfully it is only 8 attributes.
    – iphigenie
    Jan 11 '18 at 13:01














    saved my day bro
    – Vinod Kumar
    Jul 3 '18 at 17:52




    saved my day bro
    – Vinod Kumar
    Jul 3 '18 at 17:52













    0














    The steps to resolve this issue after migrating is first to open the attribute and save it again, this will set the type from text to varchar. After this run the SQL below to copy all data from the text to the varchar table.



    INSERT IGNORE INTO catalog_product_entity_varchar (store_id, attribute_id, entity_id, value)select store_id, attribute_id, entity_id, value from catalog_product_entity_text where catalog_product_entity_text.attribute_id = {your attribute id} and catalog_product_entity_text.value is not null;


    Now delete the data from the text table



    DELETE FROM `catalog_product_entity_text` WHERE `attribute_id` = {your attribute id}


    Run in terminal




    • php magento2/bin/magento indexer:reindex

    • php magento2/bin/magento cache:flush


    If the reindex is giving a duplication error, search for the entity_id in the catalog_product_entity_varchar table and check if there is a duplicate value for the attribute id in the field.






    share|improve this answer








    New contributor




    Dennis van der Graaf is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.























      0














      The steps to resolve this issue after migrating is first to open the attribute and save it again, this will set the type from text to varchar. After this run the SQL below to copy all data from the text to the varchar table.



      INSERT IGNORE INTO catalog_product_entity_varchar (store_id, attribute_id, entity_id, value)select store_id, attribute_id, entity_id, value from catalog_product_entity_text where catalog_product_entity_text.attribute_id = {your attribute id} and catalog_product_entity_text.value is not null;


      Now delete the data from the text table



      DELETE FROM `catalog_product_entity_text` WHERE `attribute_id` = {your attribute id}


      Run in terminal




      • php magento2/bin/magento indexer:reindex

      • php magento2/bin/magento cache:flush


      If the reindex is giving a duplication error, search for the entity_id in the catalog_product_entity_varchar table and check if there is a duplicate value for the attribute id in the field.






      share|improve this answer








      New contributor




      Dennis van der Graaf is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.





















        0












        0








        0






        The steps to resolve this issue after migrating is first to open the attribute and save it again, this will set the type from text to varchar. After this run the SQL below to copy all data from the text to the varchar table.



        INSERT IGNORE INTO catalog_product_entity_varchar (store_id, attribute_id, entity_id, value)select store_id, attribute_id, entity_id, value from catalog_product_entity_text where catalog_product_entity_text.attribute_id = {your attribute id} and catalog_product_entity_text.value is not null;


        Now delete the data from the text table



        DELETE FROM `catalog_product_entity_text` WHERE `attribute_id` = {your attribute id}


        Run in terminal




        • php magento2/bin/magento indexer:reindex

        • php magento2/bin/magento cache:flush


        If the reindex is giving a duplication error, search for the entity_id in the catalog_product_entity_varchar table and check if there is a duplicate value for the attribute id in the field.






        share|improve this answer








        New contributor




        Dennis van der Graaf is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.









        The steps to resolve this issue after migrating is first to open the attribute and save it again, this will set the type from text to varchar. After this run the SQL below to copy all data from the text to the varchar table.



        INSERT IGNORE INTO catalog_product_entity_varchar (store_id, attribute_id, entity_id, value)select store_id, attribute_id, entity_id, value from catalog_product_entity_text where catalog_product_entity_text.attribute_id = {your attribute id} and catalog_product_entity_text.value is not null;


        Now delete the data from the text table



        DELETE FROM `catalog_product_entity_text` WHERE `attribute_id` = {your attribute id}


        Run in terminal




        • php magento2/bin/magento indexer:reindex

        • php magento2/bin/magento cache:flush


        If the reindex is giving a duplication error, search for the entity_id in the catalog_product_entity_varchar table and check if there is a duplicate value for the attribute id in the field.







        share|improve this answer








        New contributor




        Dennis van der Graaf is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.









        share|improve this answer



        share|improve this answer






        New contributor




        Dennis van der Graaf is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.









        answered yesterday









        Dennis van der Graaf

        1




        1




        New contributor




        Dennis van der Graaf is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.





        New contributor





        Dennis van der Graaf is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.






        Dennis van der Graaf is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.






























            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.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • 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%2f192323%2fattribute-not-shown-in-layer-navigation%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

            1300-talet

            1300-talet

            Display a custom attribute below product name in the front-end Magento 1.9.3.8