Import product CSV url_key for the default (without store_view_code) should not update the url key in the frontend

[erwinschaap]

Preconditions and environment

• Magento version 2.4.3
• Anything else that would help a developer reproduce the bug: multistore setup with products

Steps to reproduce

1. Create one product and update the url key so in each store view there is a different url key (see result for an example)
2. After the creation, upload a product import CSV with that specific product sku, store_view_code empty and for the url_key a different URL-key than already used in the product (see result for an example)

Expected result

The default URL key is updating to the new url key and for the specific store_views the value for the url_key in the backoffice AS in the frontend visible is the same

default: jacked
en: (default) jacked
nl: jas
fr: veste

import for default:
sku,store_view_code,url_key
1,,jack

backoffice:
default: jack
en: (default) jack
nl: jas
fr: veste

frontend:
default: jack
en: (default) jack
nl: jas
fr: veste

The overrides are still doing their work.. This is expected

Actual result

The url_key in the backoffice for a specific store view is still the initial url_key provided by the store, but the url_key in the frontend visible is now the url_key uploaded by product CSV import.

default: jacked
en: (default) jacked
nl: jas
fr: veste

import for default:
sku,store_view_code,url_key
1,,jack

backoffice:
default: jack
en: (default) jack
nl: jas
fr: veste

frontend:
default: jack
en: (default) jack
nl: jack
fr: jack

So all urls in the frontend are now the same url for each store but in the backoffice there are overiddes. This is NOT correct!

Additional information

No response

Release note

No response

Triage and priority

• 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”.

[m2-assistant]

Hi @erwinschaap. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant]

Hi @engcom-Dash. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
     Details

     - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
     - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
     - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[engcom-Dash]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @engcom-Dash. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @engcom-Dash, here is your Magento Instance: https://d9dca40b3d4faa95725e11adcc8682e0.instances.magento-community.engineering
Admin access: https://d9dca40b3d4faa95725e11adcc8682e0.instances.magento-community.engineering/admin_eee2
Login: 80ffc8d7
Password: 9e9594249150

[engcom-Dash]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @engcom-Dash. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @engcom-Dash, here is your Magento Instance: https://d9dca40b3d4faa95725e11adcc8682e0.instances.magento-community.engineering
Admin access: https://d9dca40b3d4faa95725e11adcc8682e0.instances.magento-community.engineering/admin_be27
Login: fdd434e2
Password: 14c2d499e8d0

[engcom-Dash]

Hi @erwinschaap ,

Could you please the share CSV file which you are utilising while import to reproduce the issue.That would be helpful for us to understand the expected result more clearly.

Thanks.

[ryanpalmerweb]

We are experiencing this issue on 2.4.5-p1 too, the url keys for the store views in the admin area are ignored and the frontend is still using default scope url keys, "use default" is not ticked.