-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
main_table prefix on exception company_name #31764
Comments
Hi @DavaGordon. Thank you for your report.
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:
For more details, please, review the Magento Contributor Assistant documentation. Please, add a comment to assign the issue:
🕙 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, please join the Community Contributions Triage session to discuss the appropriate ticket. 🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel ✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel |
Hi @DavaGordon, I couldn't reproduce this issue on 2.4, can you confirm the steps and how to reproduce such problem? Thanks. |
Magneto 2 EE (2.3.6) / B2B Module / Magneto Cloud Steps Filter by company name issue occurred reason for this is the reference of company name was coming from the company table which was not in the main table so when we filtered by company we received this issue. this was tested across 3 seperate websites all using similar environment specs and with all none standard magento modules disabled. Outcome
Always returned true as a result the it returning true the prefix of main_table was added to company_name which if you look at the overall code did no exist in the customer_grid_flat table as we had the company module active so the code should have returned false and retrieved the value from the company.company_name rather than customer_grid_flat(main_table).company_name The code below which was put in place on all 3 environments checks the main_table index to check if the column is valid if returns true it will append the main_table prefix otherwise the reference will look in the correct place which is the company table
Tested 3 environments no link in code base 3 seperate companies all same issue. fix resolves issue for all 3 |
This bug occurs in Magento 2.3.7-pt2 as well. Default Magento does not have Company fields setup but once customers are linked to companies, I believe it's not hard to reproduce this error. |
Solved this on our platform with a before plugin.
|
It's not really necessary to reproduce this ticket in order to see that this problem exists. The list of columns in By default, company_name (as in the search fields) is not in |
@danieluniform did u try reindexing? being a flat table it should add the missing column as it happened for me |
Hi @engcom-November. Thank you for working on this issue.
|
✅ Jira issue https://jira.corp.adobe.com/browse/AC-6683 is successfully created for this GitHub issue. |
✅ Confirmed by @engcom-November. Thank you for verifying the issue. |
Hello, Internal team has started to work on it Thanks. |
No description provided.
The text was updated successfully, but these errors were encountered: