Skip to main content

How to add new field in attribute form in Magento 2?

Magento provide a feature to manage product attributes from the admin. There we can manage how to use that attributes in frontend and backend. And sometimes based on demand, we need additional information for an individual attribute. For example, include an attribute in the product feed.

So let's see how we can add a new field to capture the additional value for each attribute. Please follow the below steps:

STEP 1: Create a plugin

<config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:nonamespaceschemalocation="urn:magento:framework:ObjectManager/etc/config.xsd">
    <type name="Magento\Catalog\Block\Adminhtml\Product\Attribute\Edit\Tab\Front">
        <plugin name="extension_attribute_edit_form" sortorder="1" type="MageInsight\ProductFeed\Plugin\Block\Adminhtml\Product\Attribute\Edit\Tab\Front">
    </plugin></type>
</config>

STEP 2: Next, we will create the “Front” class inside the Plugin folder which will contain the logic of adding a field in the form.

<?php
namespace MageInsight\ProductFeed\Plugin\Block\Adminhtml\Product\Attribute\Edit\Tab;

class Front
{

    protected $booleanSource;

    protected $registry;

    public function __construct(
        \Magento\Config\Model\Config\Source\Yesno $booleanSource,
        \Magento\Framework\Registry $registry
    ) {
        $this->booleanSource = $booleanSource;
        $this->registry = $registry;
    }

    public function aroundGetFormHtml(
        \Magento\Catalog\Block\Adminhtml\Product\Attribute\Edit\Tab\Front $subject,
        \Closure $proceed
    )
    {
        $booleanSource = $this->booleanSource->toOptionArray();
        $attributeObject = $this->getAttributeObject();
        $form = $subject->getForm();
        $fieldset = $form->getElement('front_fieldset');
        $fieldset->addField(
            'used_in_feed',
            'select',
            [
                'name' => 'used_in_feed',
                'label' => __('Used in Feed'),
                'title' => __('Used in Feed'),
                'value' => $attributeObject->getData('used_in_feed'),
                'values' => $booleanSource,
            ]
        );
        return $proceed();
    }

    private function getAttributeObject()
    {
        return $this->registry->registry('entity_attribute');
    }
}

STEP 3: Once this plugin is created, we can see the new filed in the Product attribute form. Now we need to add the new field in database so we need to add a new column in catalog_eav_attribute table as below:

<schema xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:noNamespaceSchemaLocation="urn:magento:framework:Setup/Declaration/Schema/etc/schema.xsd">
    <table name="catalog_eav_attribute" resource="default" engine="innodb" comment="Catalog EAV Attribute Table">
        <column xsi:type="smallint" name="used_in_feed" unsigned="true" nullable="false" identity="false" default="0" comment="Used in Feed"/>
   </table>
</schema>

Now just execute upgrade command from the command line and your new field is ready to use.

Comments

Popular posts from this blog

Unlocking Success: The Vital Role of the Contact Us Page in E-commerce

In the dynamic realm of e-commerce, where digital transactions reign supreme, the significance of customer communication cannot be overstated. Amidst the plethora of factors influencing the success of an online store, one often overlooked yet fundamentally important element is the Contact Us page. This seemingly humble corner of a website holds immense power, serving as a linchpin in fostering trust, resolving issues, and nurturing customer relationships. Let's delve deeper into why the Contact Us page is not just an afterthought but a strategic asset for e-commerce businesses, backed by proven data. Building Trust and Credibility Trust is the cornerstone of any successful e-commerce venture. According to a survey conducted by Edelman, 81% of consumers say that trusting a brand to do what is right is a deciding factor in their purchasing decisions. A prominently displayed Contact Us page with clear contact information, including a physical address, phone number, and email address, ...

Magento - LogRocket Integration

In today’s competitive eCommerce landscape, understanding user behavior is crucial for optimizing customer experiences and improving conversion rates. Magento 2, a powerful and flexible eCommerce platform, allows merchants to customize their online stores extensively. However, monitoring how users interact with these customizations is often challenging. This is where LogRocket, a modern session replay tool, comes into play. Integrating LogRocket with Magento 2 can provide invaluable insights into user behavior, performance bottlenecks, and UX issues. In this blog post, we’ll walk you through the steps to integrate LogRocket with Magento 2, and how this integration can help you improve your store’s performance and user experience. What is LogRocket? LogRocket is a session replay tool that enables you to record and playback user activity on your website. It tracks interactions such as clicks, scrolls, and form inputs, giving you a clear view of how users navigate your store. In addition,...

Using Composer Update is a Crime: Why Magento Developers Should Avoid It

As a Magento developer, managing third-party modules via Composer is essential for keeping your project organized and up to date. However, when installing a new module, there’s one command that might seem tempting, yet can lead to chaos if not used carefully: composer update Yes, you read that right—using composer update can be a crime (against your project, that is). In this blog, we’ll explore why running composer update without caution can be risky, and why you should think twice before pulling the trigger. Let’s break it down. What Does composer update Do? At first glance, composer update seems harmless. When you run it, Composer checks for newer versions of every package listed in your composer.json file and updates them to the latest compatible versions based on your version constraints. That sounds good, right? Why wouldn't you want the latest updates? Well, here's where things get tricky. The Hidden Risk of composer update Running composer update doesn't just u...