Important
You are browsing upcoming documentation for version 7.1 of OroCommerce, scheduled for release in 2027. Read the documentation for the latest LTS version to get up-to-date information.
See our Release Process documentation for more information on the currently supported and upcoming releases.
CLI Commands (CustomerPartNumberBundle)
Both commands below are feature-gated by the oro_customer_part_number feature. For a step-by-step guide on
using them together to move off the legacy OroLab implementation, see Migrating from the Legacy OroLab
Bundle.
oro:customer-part-number:migrate-from-orolab
The oro:customer-part-number:migrate-from-orolab command copies customer part numbers from the legacy
orolab_customer_part_number table into the new oro_customer_part_number table.
Note
Migrations\Schema\OroCustomerPartNumberInstaller runs this migration automatically the first time
this bundle’s schema is installed - on a brand-new application install, or when this bundle is newly added to
an already-installed application and oro:platform:update is run - provided the legacy
orolab_customer_part_number table already exists at that point. Run this command manually only if the
legacy table did not exist yet at that time, or to re-run the migration (e.g., with --dry-run).
php bin/console oro:customer-part-number:migrate-from-orolab
Options:
--dry-run- report what would be migrated without writing anything to the database.php bin/console oro:customer-part-number:migrate-from-orolab --dry-run
--batch-size- number of source rows read per batch (default1000).php bin/console oro:customer-part-number:migrate-from-orolab --batch-size=500
oro:customer-part-number:cleanup-orolab
The oro:customer-part-number:cleanup-orolab command removes the legacy OroLab CustomerPartNumber entity
configuration.
Also removes the extended
customerrelation and its inversepartNumbersrelation onCustomer.Asks for confirmation by default, since it removes entity configuration and extended relations.
php bin/console oro:customer-part-number:cleanup-orolab
Options:
--force- skip the confirmation prompt, for use in a non-interactive environment.php bin/console oro:customer-part-number:cleanup-orolab --force
Note
The legacy table orolab_customer_part_number and its columns are intentionally NOT dropped by this
command, so the data is retained and can be removed manually later. The command is idempotent and safe to
run multiple times.