Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Customer Import: update to disable_auto_group_change ignored #36409

Closed
1 of 5 tasks
nbennett25 opened this issue Nov 2, 2022 · 26 comments · Fixed by #36496
Closed
1 of 5 tasks

Customer Import: update to disable_auto_group_change ignored #36409

nbennett25 opened this issue Nov 2, 2022 · 26 comments · Fixed by #36496
Assignees
Labels
Area: Account Component: CustomerImportExport Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: done Reported on 2.3.5-p2 Indicates original Magento version for the Issue report. Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch

Comments

@nbennett25
Copy link

nbennett25 commented Nov 2, 2022

Preconditions and environment

1.Magento 2.3.5-p2
2.Customer exists

Steps to reproduce

  1. Go to System > Import/Export > Export
  2. Select type: Customer Main File
  3. Export Customer record
  4. In downloaded file, strip out all non-required fields except for disable_auto_group_change
  5. Change disable_auto_group_change value(if the customer already has the disable auto group change checked in their customer record, switch the 1 above to 0)
  6. Go to System > Import/Export > Import
  7. Select Type: Customer Main File
  8. Select Import Behavior: Add/Update Complex Data
  9. Upload File
  10. Check Data
  11. Import File

Expected result

  1. Customer record shows change in 'Disable Automatic Group Change Based on VAT ID' setting.

Actual result

  1. No changes in 'Disable Automatic Group Change Based on VAT ID' setting.

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
Copy link

m2-assistant bot commented Nov 2, 2022

Hi @nbennett25. Thank you for your report.
To speed up processing of this issue, make sure that you provided the following information:

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

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.


⚠️ 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.

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

@nbennett25
Copy link
Author

@magento give me 2.4-develop instance

@magento-deployment-service
Copy link

Hi @nbennett25. Thank you for your request. I'm working on Magento instance for you.

@magento-deployment-service
Copy link

@nbennett25
Copy link
Author

Confirmed in 2.4-develop

@engcom-Bravo engcom-Bravo self-assigned this Nov 2, 2022
@m2-assistant
Copy link

m2-assistant bot commented Nov 2, 2022

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

    DetailsIf 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.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!

  • 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-Bravo engcom-Bravo added the Reported on 2.3.5-p2 Indicates original Magento version for the Issue report. label Nov 2, 2022
@engcom-Bravo
Copy link
Contributor

@magento give me 2.4-develop instance

@magento-deployment-service
Copy link

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

@magento-deployment-service
Copy link

@engcom-Bravo
Copy link
Contributor

Hi @nbennett25,

Thank you for reporting and collaboration.
Verified the issue on Magento 2.4-develop instance we are not able to reproduce the issue.Kindly Provide more information about disable_auto_group_change value and also provide exact steps to reproduce the issue and screenshots if required.

Kindly provide your CSV file it is helpful for us.

Thanks.

@engcom-Bravo engcom-Bravo added the Issue: needs update Additional information is require, waiting for response label Nov 4, 2022
@m2-community-project m2-community-project bot moved this from Ready for Confirmation to Needs Update in Issue Confirmation and Triage Board Nov 4, 2022
@nbennett25
Copy link
Author

@engcom-Bravo I was able to reproduce this on the 2.4-develop instance provided. The csv content will be determined by the customer records (specifically email address), but the base of it is below:

_website,email,disable_auto_group_change
base,[customer email],1

@engcom-Bravo
Copy link
Contributor

Hi @nbennett25,

Thanks for your update.

We tired to reproduce the issue but we are not able to reproduce the issue.we Followed these steps

1.Go to System > Import/Export > Export
2.Select type: Customer Main File
3.Export Customer record

We got Customer File :

export_customer_20221110_010422.csv

Kindly Provide more information about In downloaded file, strip out all non-required fields except for disable_auto_group_change,Change disable_auto_group_change value. It will helpful for us to proceed further.

Thanks.

@nbennett25
Copy link
Author

@engcom-Bravo is there a way to attach files to a comment..? Please try creating a csv with the following (based on your file):

email,_website,_store,disable_auto_group_change
roni_cost@example.com,base,default,1

Then Import the file via System > Import/Export > Import, Customer Main File. (if the customer already has the disable auto group change checked in their customer record, switch the 1 above to 0 to flag the change.

@engcom-Bravo
Copy link
Contributor

@magento give me 2.4-develop instance

@magento-deployment-service
Copy link

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

@magento-deployment-service
Copy link

@engcom-Bravo
Copy link
Contributor

Hi @nbennett25,

Thanks for your Update.

You can attach files through a comment.

Screenshot 2022-11-11 at 5 11 38 PM

Kindly attach.

Thanks.

@nbennett25
Copy link
Author

Here's a csv version of the above @engcom-Bravo:

auto_group_change.csv

@engcom-Bravo
Copy link
Contributor

@magento give me 2.4-develop instance

@magento-deployment-service
Copy link

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

@magento-deployment-service
Copy link

@engcom-Bravo
Copy link
Contributor

Hi @nbennett25,

Thanks for your update.

Verified the issue on Magento 2.4-develop instance and the issue is reproducible.

Customer Import: update to disable_auto_group_change was ignored.

Steps to reproduce

1.Go to System > Import/Export > Export
2.Select type: Customer Main File
3.Export Customer record
4.In downloaded file, strip out all non-required fields except for disable_auto_group_change
5.Change disable_auto_group_change value(if the customer already has the disable auto group change checked in their customer record, switch the 1 above to 0)
6.Go to System > Import/Export > Import
7.Select Type: Customer Main File
8.Select Import Behavior: Add/Update Complex Data
9.Upload File
10.Check Data
11.Import File

We have used Below CSV file (existing customers) we changed disable_auto_group_change to 1 there is No changes in 'Disable Automatic Group Change Based on VAT ID'

five.csv

Hence confirming this issue.

Thanks.

@engcom-Bravo engcom-Bravo removed the Issue: needs update Additional information is require, waiting for response label Nov 16, 2022
@engcom-Hotel engcom-Hotel added the Priority: P2 A defect with this priority could have functionality issues which are not to expectations. label Nov 17, 2022
@m2-community-project m2-community-project bot added this to Ready for Development in High Priority Backlog Nov 17, 2022
@Vasudev-22
Copy link
Contributor

@magento I am working on this

@engcom-Bravo
Copy link
Contributor

Hello,

The internal team has started working on the issue.

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Account Component: CustomerImportExport Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: done Reported on 2.3.5-p2 Indicates original Magento version for the Issue report. Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch
Projects
Development

Successfully merging a pull request may close this issue.

5 participants