Fixing Greyed Out Options for Custom Stock Status Attribute

In my instance, all options for Custom Stock Status attribute are greyed out and I’m not able to edit them or add new ones

      The issue arises due to the reset entity in the DB that happens during module update/installation. In order to fix it, you need to modify the value of the is_user_defined entity in the DB.
This could be done with the following command:

UPDATE tableprefixeav_attribute SET is_user_defined = 1 WHERE attribute_code = 'custom_stock_status';
      In the command, please substitute the 'tableprefix' text with the table name corresponding to your instance. You can find the name of the table in the file app/etc/env.php:



      Alternatively, you can do the same manually via a DB manager you’re using (instead of running a command) - update the value of the entity and save the changes.
      If you face any difficulties, please contact our support team

      • Related Articles

      • Custom Stock Status API

        We have created a public API collection for Custom Stock Status module with all available queries and sample data that you can both test via our demo endpoints and copy to run local tests in your Magento environment. More details about using public ...
      • Can I edit the quotes?

        Since v. 2.11.0 of Request a Quote extension, we have added a feature to include simple, virtual, and downloadable out-of-stock products when creating quotes. You can find the ‘amasty/module-request-quote-edit’ package for installing in composer ...
      • Custom Stock Status | GraphQL methods

        Query getAmCustomStockStatus description: get information about a stock status
      • Is it possible to add a custom attribute (Brand, SKU, etc.) to the list of sorting options?

        Our Improved Sorting module extends the standard Magento sorting by adding new sorting options which are: Best Sellers, Top Rated, Most Viewed, etc. Nevertheless, it is possible to add a new option to the sorting list using the default Magento ...
      • The changes applied to custom options do not reflect the storefront. How to fix that?

        If an option name changed in the Product Option Templates module does not reflect your storefront, the most likely cause is store‑view scoping. On affected non‑default store views, the "Use Default Value" checkbox seems to be unchecked for the option ...