Skip to content

Default created storeview sales sequences are missing a prefix #30863

Open
@hostep

Description

@hostep

Preconditions (*)

Magento 2.4-develop

Steps to reproduce (*)

  1. Setup a Magento 2 shop (doesn't matter which version, this has been bugged since forever)
  2. Look at the sales_sequence_profile table in the database.

Expected result (*)

  1. The profiles associated to storeview ID 1 should have as prefix 1

Actual result (*)

  1. The profiles associated to storeview ID 1 have as prefix NULL

DB prefix

Discussion

When creating a second storeview, it gets prefix 2, so one would expect that the default storeview which is created when setting up a shop gets prefix 1.

When this gets fixed, it should only be fixed for new Magento shops being setup, please don't add a db migration script to fix it for existing shops, that would be very unexpected for shop owners.

Workaround

The following SQL can be executed as a workaround if you want the prefix to be set correctly/consistently with other storeviews:

UPDATE `sales_sequence_profile`
SET `prefix` = 1
WHERE `profile_id` IN
    (SELECT `meta_id`
     FROM `sales_sequence_meta`
     WHERE `store_id` = 1);

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

  • Severity: S0 - Affects critical data or functionality and leaves users without workaround.
  • Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
  • Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
  • Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
  • Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

Metadata

Metadata

Assignees

Labels

Component: SalesComponent: StoreIssue: ConfirmedGate 3 Passed. Manual verification of the issue completed. Issue is confirmedIssue: ready for confirmationPriority: P2A defect with this priority could have functionality issues which are not to expectations.Progress: PR in progressReported on 2.4.xIndicates original Magento version for the Issue report.Reproduced on 2.4.xThe issue has been reproduced on latest 2.4-develop branchSeverity: S3Affects non-critical data or functionality and does not force users to employ a workaround.

Type

No type

Projects

Status

Pull Request In Progress

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions