<?= $block->escapeJs($value) ?>

<?= $block->escapeJsVar($value) ?>

<?= $block->renderJs($value) ?>

<?= $block->escapeHtml($value) ?>

Utilize the SalesSetup class’ addAttribute method.

Ensure your UpgradeSchema class extends CoreSetup and call $this->addSalesColumns().

On the ModuleDataSetupInterface, call $setup->getSales()->addColumn()

On the default EavSetup class, utilize the addColumn method.

Add the getAttributeExtensions() method and implement ExtensionAttributesInterface in each model.

Configure your models in etc/extension_attributes.xml.

Create a ExtensionAttributeInterface for each model.

Ensure each model extends Magento\Framework\Model\AbstractExtensibleModel.

Use a dependencies node in your indexer configuration.

Use a plugin on the IndexManager class to change load order.

Specify the sortOrder in your indexer configuration.

Create a bash script to execute each indexer in the correct order.

Add the fields into a <fieldset> node in the existing form in the ui_component XML file

Add a new form for the field group in the ui_component XML file

Add the fields into <tab> nodes in the customer_account_edit.xml layout file

Create a plugin for the method
MyCompany\MyModule\Block\Adminhtml\Form\Edit\Tabs::toHtml()

Remove the generated child class from generated/code that is calling the parent constructor with the old signature

Configure the new argument in di.xml for the controller class

Clean the config cache that contains all constructor signatures

New dependencies must be added at the end of the constructor signature because dependencies cannot be added in the middle of existing constructors

You add an extension attribute to Magento\Sales\Api\Data\OrderInterface to include the new field

You update Magento\Sales\Api\OrderManagementInterface and
Magento\Sales\Api\Data\OrderInterface to add your field

You create an install script to add a column to the sales table and Magento will automatically pull in the information

You create an etc/webapi.xml file and add the new field as an item to the route, as shown in the following code: <route url="/V1/orders" method="GET">
<service class= "Magento\Sales\Api\OrderRepositoryInterface" method="getList"> <item name="my_new_attribute" xsi:type="string" /> </service>
<resources> <resource ref="Magento_Sales::sales" /> </resources>
</route>

It cleans the segment and customer related entities from the session

It cleans the intermediate data of the segment-website and the segment-customer mapping in the tables to improve performance

It passes the segment information to the HttpContext from the customer session

It passes the segment information to the Knockout JS model from the customer session