Incorrect behaviour of export/import logic for product with datetime attribute

[staradzinau]

Preconditions (*)

1. Magento 2.3.3 or 2.3-develop
2. Set Locale to "English (United Kingdom)"
3. Default County: United States
4. Product attribute with "Catalog Input Type for Store Owner" => 'Date' (for example - 'test_date_attribute')
5. Add this attribute to default attribute set
6. Simple product with date attribute 'test_date_attribute' is created. (SKU = 'test-product-sku')

Scenario 1
Steps to reproduce

1. Set some date for the 'test_date_attribute' attribute for product 'test-product-sku'. (Day of the month should be greater than 12)
   
2. Go to System -> Export, perform products export operation to create a CSV, which contains product 'test-product-sku' with the value of 'test_date_attribute' attribute
   

Expected result (*)

Value of 'test_date_attribute' attribute in the product creation page is formatted according to the current locale

Actual result (*)

The format of the attribute value 'test_date_attribute' on the product creation page does not match the current locale

Scenario 2
Steps to reproduce

1. Go to System -> Import, choose 'Products' entity type, upload CSV form the previous scenario, and click on "Sheck Data" button

Expected result (*)

Exported data is validated correctly, the "Import" button is shown

Actual result (*)

Format of the value of 'test_date_attribute' attribute in the product creation page, do not correspond to the current locale. Exported data validation is failed

Additional information

After manual modifying of the date format to the US one inside CSV file, validation works correctly, import operation works fine

[m2-assistant]

Hi @avgust1111. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.3-develop instance - upcoming 2.3.x release

For more details, please, review the Magento Contributor Assistant documentation.

@avgust1111 do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

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

[staradzinau]

@magento give me 2.3-develop instance

[magento-engcom-team]

Hi @avgust1111. Thank you for your request. I'm working on Magento 2.3-develop instance for you

[magento-engcom-team]

Hi @avgust1111, here is your Magento instance.
Admin access: https://i-25700-2-3-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[staradzinau]

It's impossible to reproduce the issue within the provided Magento instance: running cron job is required for fetching export results (CSV file). Seems like specified M2 instance doesn't have running cron job

[m2-assistant]

Hi @engcom-Echo. 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).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.3-develop branch

  Details

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

• 5. Add label Issue: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Echo]

Hello @avgust1111

Thank you for your report and collaboration!
We are not able to reproduce this issue by provided steps.
Tested on 2.3-develop and 2.3.3

Testing scenario:

Preconditions:

1. Default locale - United States
2. Product attribute with "Catalog Input Type for Store Owner" => 'Date' (for example - 'test_date_attribute')
3. Add this attribute to default attribute set
4. Simple product with date attribute 'test_date_attribute' is created. (SKU = 'test-product-sku')

Scenario 1
Steps to reproduce

1. Set some date for the 'test_date_attribute' attribute for product 'test-product-sku'. (Day of the month should be greater than 12)
2. Go to System -> Export, perform products export operation to create a CSV, which contains product 'test-product-sku' with the value of 'test_date_attribute' attribute

Result
Value of 'test_date_attribute' attribute in the CSV is formatted according to the current locale

Scenario 2

Steps to reproduce

1. Go to System -> Import, choose 'Products' entity type, upload CSV form the previous scenario, and click on "Sheck Data" button

Result
Exported data is validated correctly, the "Import" button is shown

Thank you!

[staradzinau]

Hello, @engcom-Echo !
Thank you for the quick feedback

Please, check, which county is used in the "Country options" section in the "General" tab?
Had your CSV export file been generated by cron, after some delay?

I've reproduced the same issue on the 2.3.3 installation with native sample data, all the dates in the CSV export file have the incorrect format, please, look:


Month and day aren't compatible with US date format

[engcom-Echo]

Hello @avgust1111

Here is my Settings (M 2.3.3)

All my CSV export files has been generated by cron after some delay.
All files have the correct date format.

Could you provide more details for reproduce this issue?
Please add screenshots of the attribute settings.

Thank you!

[staradzinau]

Hello, @engcom-Echo !

Thank you for the update.
I've checked settings again and found the option, which triggers misbehavior for import/export. In my test environment with native M2 sample data installed, 'Locale" has been set to "English (United Kingdom)". So, if you set in "Stores" -> "Configuration" -> "General" -> "General" -> Country Options -> Default County: United States, and in "Stores" -> "Configuration" -> "General" -> "General" -> Locale Options -> Locale: "English (United Kingdom)", your exported CSV file will contain dates in the wrong format
Sorry for incomplete steps to reproduce
Please, check this case

Thank you!

[magento-engcom-team]

✅ Confirmed by @engcom-Echo
Thank you for verifying the issue. Based on the provided information internal tickets MC-29131 were created

Issue Available: @engcom-Echo, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[m2-assistant]

Hi @sanjay-wagento. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

• 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 2. 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!

• 3. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

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

[sanjay-wagento]

#MM20IN