• v5.0
    • Versions
    • master

 

  • Install Akeneo PIM
    • Install Akeneo PIM for development with Docker
    • Install Akeneo PIM manually
      • System Requirements
      • System installation on Debian 10 (Buster)
      • System installation on Ubuntu 18.04 (Bionic Beaver)
      • System installation on Ubuntu 20.04 (Focal Fossa)
      • Installing Akeneo PIM Community Edition (CE)
      • Installing Akeneo PIM Enterprise Edition (EE) with the Archive
      • Setting up the job queue daemon
      • Setting up the Events API
    • How to customize the Dataset
    • How to Add Translation Packs
  • Upgrade Akeneo PIM projects
    • How to apply a patch?
      • How to apply a patch - Community Edition
      • How to apply a patch - Enterprise Edition - Flexibility Cloud offer
      • How to apply a patch - Enterprise Edition - On Premise offer
    • Where is the Changelog?
    • How to upgrade to a minor version?
    • How to upgrade to a major version?
      • Upgrade from 3.2 to 4.0
      • Upgrade from 4.0 to 5.0
  • Import and Export data
    • How import works
    • Understanding the Product Import
    • Understanding the Product Export
    • Formats
      • Localized labels
      • Scopable labels
      • Association types data structure
      • Attribute data structure
      • Category data structure
      • Family data structure
      • Family variant data structure
      • Group data structure
      • Options data structure
      • Product data structure
      • Product model data structure
    • Akeneo Connectors
    • How to Customize Import / Export
      • How to create a new Connector
      • How to import Products from a XML file
      • How to clean a CSV file during a Product import
      • How to automate imports/exports
  • Manipulate the Akeneo PIM data
    • How to Customize Mass Edit Operations
      • How to register a new bulk action
      • How to Register a New Mass Edit Action on Products
    • How to Manipulate Products
      • How to Query Products
      • How to Create Products
      • How to Update Products
      • How to Validate Products
      • How to Save Products
      • How to Remove Products
    • How to Manipulate Non-Product Objects
      • How to Query Non-Product Objects
      • How to Create Non-Product Objects
      • How to Update Non-Product Objects
      • How to Validate Non-Product Objects
      • How to Save Non-Product Objects
      • How to Remove Non-Product Objects
    • How to add a custom action rule
      • General information about rule format
      • How to add a custom action in the rule engine
    • How to Define Access Control List
    • How to Customize the Catalog Structure
      • How to Create a Reference Data
    • How To Customize Teamwork Assistant (Enterprise Edition)
      • Customize notifications
      • Add a calculation step
      • How to log calculation step
      • Remove projects impacted by a custom catalog update
    • How to store assets externally
    • How to Configure Measurement Limits
  • Maintain Akeneo PIM projects
    • First aid kit
    • Bug qualification
    • Common issues
    • Scalability Guide
      • Audit with 3 Representative Catalogs
      • More than 10k attributes?
      • More than 10k families?
      • More than 10k categories?
      • More than 500 attributes usable in the product grids?
      • More than 100k products to export?
      • More than 1GB of product media to export?
    • How to purge history
      • How to Purge jobs executions
      • How to adapt the version purger to your needs
  • Contribute to Akeneo PIM
    • How to report an issue?
    • How to translate the user interface?
    • How to enhance the documentation?
    • How to contribute to a Connector?
    • How to submit a patch to the PIM?
    • How to contribute to the frontend part of the application
    • How behavior tests are architectured in the PIM?
      • Establishing Decorator Pattern
      • Using Spin In Behat
  • Use SSO authentication locally
  • Reference Entities
    • Configure Entity Limits
    • Create a new Reference Entity Attribute type
    • Enrich Records with a new Reference Entity Attribute type
    • Add a Custom Property to Your Custom Attribute Type
    • Refresh records completeness
  • Troubleshooting guide
  • Technical overview
    • Product Information
    • Teamwork Assistant (Enterprise Edition)
      • Project creation
      • Project completeness
      • Project Completeness widget
      • Catalog update impact
      • Scalability guide
      • Users permission summary for Behat tests
    • Collaborative workflow
      • Simple workflow
      • Partial workflow
  • Technical architecture
    • Best Practices
      • Create a project
      • Create a reusable bundle
      • Code Conventions
      • Coding Standards
    • How to implement your business logic using the event system
    • Events
      • Storage events
      • Workflow events (Enterprise Edition only)
    • How to Localize your data
      • How to change the PIM locale
      • How to Use Localizers
      • How to use Presenters
    • How to Add a Notification
    • Performances Guide
      • Memory usage of rules execution (Enterprise Edition)
      • Memory leak fix in Rules Engine (ORM)
      • More than 100 WYSIWYG editors in a page
      • PHP7 and HHVM Compatibility?
      • Job product batch size
    • How to Use the Web REST API
    • Standard format
      • Products
      • Other entities
      • Usage
    • Application Technical Information
      • Application Technical Dependencies
      • Server side set up for hosting
      • System Requirements
      • Recommended configuration
      • Client side configuration and compatibilities
      • Operation processes
      • Flow Matrix
  • Akeneo Cloud Edition
    • Flexibility
      • Environment accesses
      • System Administration & Services Management
      • Periodic tasks & Crontab configuration
      • Composer settings
      • Queue Management & Workers
      • Disk Usage Management
    • Serenity
  • Akeneo Onboarder
    • Prerequisites
    • How to install the Onboarder bundle
    • Synchronization
    • How to update a minor version or to apply a patch
      • How to update the Onboarder bundle - Enterprise Edition - Flexibility Cloud offer
      • How to update the Onboarder bundle - Enterprise Edition - On Premise offer
    • How to upgrade to a major version
    • Troubleshooting
    • How to uninstall the Onboarder bundle
    • Environment variables
      • Using the DotEnv file
      • Using environment variables

How to Update Products¶

Prerequisites¶

The Akeneo PIM project introduces services to help you to manage your product objects.

As the product model is the main object of the application, the use cases are more advanced than for simple models,

  • a set of property updates on a single product (case of Product Edit Form)

  • a different set of property updates on many products (case of Product Import)

  • a similar set of property updates on many products (case of Bulk Action)

  • [put your own logic here]

We provide different services to allow you to assemble your custom “update logic”.

The default case is covered by Akeneo\Tool\Component\StorageUtils\Updater\ObjectUpdaterInterface, used to apply a set of property updates on a product.

You’ll also find some services to update a single doctrine field data or an attribute data of a product (we hide this implementation detail, attribute vs doctrine field, under the term ‘property’).

There are four services to handle this case,

  • Akeneo\Tool\Component\StorageUtils\Updater\PropertySetterInterface

  • Akeneo\Tool\Component\StorageUtils\Updater\PropertyAdderInterface

  • Akeneo\Tool\Component\StorageUtils\Updater\PropertyRemoverInterface

  • Akeneo\Tool\Component\StorageUtils\Updater\PropertyCopierInterface

Instantiate a New ObjectUpdaterInterface¶

The product updater Akeneo\Pim\Enrichment\Component\Product\Updater\ProductUpdater implements Akeneo\Tool\Component\StorageUtils\Updater\ObjectUpdaterInterface.

The product updater is available as a service, you can fetch it from the container.

$updater = $this->getContainer()->get('pim_catalog.updater.product');

Note

We provide several services which implement the same interface to update other business models (family, attribute, etc).

Warning

The updater does not validate and save the products to the database, these operations are done by the Validator and the Saver (detailed in dedicated chapters).

We target to respect the Single Responsibility Principle (SRP) in our classes, feel free to use these different services through a Facade if it facilitates your developments.

Use the ObjectUpdaterInterface¶

Now we can apply many property updates on a product.

$fieldUpdates = [
    "values" => [
        "sku"         => [["locale" => null, "scope" => null, "data" => "MySku"]],
        "description" => [["locale" => "en_US", "scope" => "mobile", "data" => "My description"]]
    ],
    "categories"  => ["tshirt", "promo"]
];

$this->updater->update($product, $fieldUpdates);

Note

The standard array format used for property updates can be obtained by normalizing product values like this, “$container->get(‘pim_serializer’)->normalize($values, ‘json’, [‘entity’ => ‘product’])”.

Instantiate a New PropertySetterInterface¶

The product property setter implements Akeneo\Tool\Component\StorageUtils\Updater\PropertySetterInterface.

It’s available as a service, you can fetch it from the container.

$propertySetter = $this->getContainer()->get('pim_catalog.updater.property_setter');

Use the PropertySetterInterface¶

The property setter allows to set a single property (doctrine field data or attribute data).

The property setter replaces the data if it already exists.

// sets data to the product name (an attribute)
$propertySetter->setData($product, 'name', 'my name', ['locale' => 'en_US', 'scope' => 'mobile']);

// sets data to the product categories (a field)
$propertySetter->setData($product, 'categories', ['category_code1', 'category_code2']);

// sets localizable and scopable attribute's data
$propertySetter->setData($product, 'description', 'my description', ['locale' => 'en_US', 'scope' => 'mobile']);

Instantiate a New PropertyAdderInterface¶

The product property adder implements Akeneo\Tool\Component\StorageUtils\Updater\PropertyAdderInterface.

It’s available as a service, you can fetch it from the container.

$propertyAdder = $this->getContainer()->get('pim_catalog.updater.property_adder');

Use the PropertyAdderInterface¶

The property adder allows to add an item to a single property (doctrine field data or attribute data) which contains a collection.

This is only available for properties that contain several items (like categories, options, prices).

The property adder keeps the existing items and adds a new item to the set.

// adds data to product colors (a multiselect attribute)
$propertyAdder->addData($product, 'color', ['red']);

// adds data to product categories (a field)
$propertyAdder->addData($product, 'categories', ['tshirt', 'promo']);

Instantiate a New PropertyRemoverInterface¶

The product property remover implements Akeneo\Tool\Component\StorageUtils\Updater\PropertyRemoverInterface.

It’s available as a service, you can fetch it from the container.

$propertyRemover = $this->getContainer()->get('pim_catalog.updater.property_remover');

Use the PropertyRemoverInterface¶

The property remover allows to remove an item from a single property (doctrine field data or attribute data) which contains a collection.

This is only available for properties that contain several items (like categories, options, prices).

The property remover keeps the existing items and removes only the provided item.

// removes the item "red" from product colors (a multiselect attribute)
$propertyRemover->removeData($product, 'color', ['red']);

// removes the product from the category "promo" (a field)
$propertyRemover->removeData($product, 'categories', ['promo']);

Instantiate a New PropertyCopierInterface¶

The product property copier implements Akeneo\Tool\Component\StorageUtils\Updater\PropertyCopierInterface.

It’s available as a service, you can fetch it from the container.

$propertyCopier = $this->getContainer()->get('pim_catalog.updater.property_copier');

Use the PropertyCopierInterface¶

The property copier allows to copy data from a property to another (doctrine field data or attribute data).

// copy the English name of the $fromProduct to the English description of the $toProduct
// note that from_scope and to_scope are also available for scopable attributes
$propertyCopier->copyData(
    $fromProduct,
    $toProduct,
    'name',
    'description',
    ['from_locale' => 'en_US', 'to_locale' => 'en_US']
);

Add a Custom FieldSetterInterface¶

If you create a new type of Attribute you need to implement the related Akeneo\Pim\Enrichment\Component\Product\Updater\Setter\AttributeSetterInterface.

If you add a doctrine field in the Product model, you need to implement the related Akeneo\Pim\Enrichment\Component\Product\Updater\Setter\FieldSetterInterface.

Both of these interfaces extend Akeneo\Pim\Enrichment\Component\Product\Updater\Setter\SetterInterface.

A setter must implement this interface and be declared as a tagged service with the tag ‘pim_catalog.updater.setter’.

Through a compiler pass, this service is finally registered in the setter registry Akeneo\Pim\Enrichment\Component\Product\Updater\Setter\SetterRegistry.

This registry is used by the product updater to know how to update a product property.

For example, assuming that you have your own ‘acme_catalog_number’ attribute type, once implemented, you could declare your setter like this:

acme_catalog.updater.setter.number_value:
    class: Acme\Bundle\CatalogBundle\Updater\Setter\CustomNumberValueSetter
    parent: pim_catalog.updater.setter.abstract
    arguments:
        - ['acme_catalog_number']
    tags:
        - { name: 'pim_catalog.updater.setter' }

Note

The best way to achieve your goal is to take a look at an existing implementation and try to find one that resembles what you want to achieve.

Add a Custom FieldAdderInterface¶

The architecture of this part is very similar to the FieldSetterInterface case, you can refer to it.

It uses its own interfaces and the service tag ‘pim_catalog.updater.adder’.

Add a Custom FieldRemoverInterface¶

The architecture of this part is very similar to the FieldSetterInterface case, you can refer to it.

It uses its own interfaces and the service tag ‘pim_catalog.updater.remover’;

Add a Custom FieldCopierInterface¶

The architecture of this part is very similar to the FieldSetterInterface case, you can refer to it.

It uses its own interfaces and the service tag ‘pim_catalog.updater.copier’;


Found a typo or a hole in the documentation and feel like contributing?
Join us on Github!