How to Trigger an Event on Magento 2 Save Store Configuration

Many times, the default Magento 2 falls short in the functionalities that are essential for an E-commerce store and hence using the events is a must thing to extend the functionality.

Magento 2 triggers admin_system_config_changed_section event after the save store config action is performed. You may want to use this event to use to get the value from a third party API and throw an error if unmatched. For example, when using the barcode generator to create barcode labels and print them, the barcode library needs to be installed. Otherwise, it throws the error.

However, to throw this error, you need to trigger an event on Magento 2 save store configuration to get the admin configuration value and use the below solution for the same.

Steps to Trigger an Event on Magento 2 Save Store Configuration:

For example, if your system.xml looks something like this:

Here, the section id is meetanshitab which has to be added in the event name as shown in the below solution:

1. Create event.xml file at app/code/Vendor/Module/etc/adminhtml/events.xml
   
   <?xml version="1.0" encoding="UTF-8"?> <config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="urn:magento:framework:Event/etc/events.xsd"> <event name="admin_system_config_changed_section_meetanshitab"> <observer name="custom_admin_system_config_changed_section_meetanshitab" instance="Vendor\Module\Observer\ConfigChange"/> </event> </config>

   1 2 3 4 5 6

   <?xml version="1.0" encoding="UTF-8"?> <config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="urn:magento:framework:Event/etc/events.xsd">     <event name="admin_system_config_changed_section_meetanshitab">         <observer name="custom_admin_system_config_changed_section_meetanshitab" instance="Vendor\Module\Observer\ConfigChange"/>     </event> </config>

2. create ConfigChange.php file at app/code/Vendor/Module/Observer/ folder
   
   <?php namespace Vendor\Module\Observer; use Magento\Framework\Event\ObserverInterface; use Magento\Framework\Event\Observer as EventObserver; use Magento\Framework\App\RequestInterface; use Magento\Framework\App\Config\Storage\WriterInterface; class ConfigChange implements ObserverInterface { private $request; private $configWriter; public function __construct(RequestInterface $request, WriterInterface $configWriter) { $this->request = $request; $this->configWriter = $configWriter; } public function execute(EventObserver $observer) { $meetParams = $this->request->getParam('groups'); $name = $meetParams['general']['fields']['name']['value']; //to print thatn value in system.log \Magento\Framework\App\ObjectManager::getInstance()->get('Psr\Log\LoggerInterface')->info($name); return $this; } } ?>

   1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25

   <?php namespace Vendor\Module\Observer; use Magento\Framework\Event\ObserverInterface; use Magento\Framework\Event\Observer as EventObserver; use Magento\Framework\App\RequestInterface; use Magento\Framework\App\Config\Storage\WriterInterface; class ConfigChange implements ObserverInterface {     private $request;     private $configWriter;     public function __construct(RequestInterface $request, WriterInterface $configWriter)     {         $this->request = $request;         $this->configWriter = $configWriter;     }     public function execute(EventObserver $observer)     {         $meetParams = $this->request->getParam('groups');         $name = $meetParams['general']['fields']['name']['value'];         //to print thatn value in system.log         \Magento\Framework\App\ObjectManager::getInstance()->get('Psr\Log\LoggerInterface')->info($name);         return $this;     } } ?>

Hope it helps.

Any doubts on the topic can be discussed in the Comments section below. I’d be happy to solve them asap.

Feel free to share the above solution with fellow developers via social media.

Thanks.