Broken Tax Rate Search Filter - SQLSTATE[23000]

[robyerevan]

Preconditions (*)

1. Magento 2.2.3

Steps to reproduce (*)

1. Go to Admin -> Stores -> Taxes -> Tax Rules
2. Add a tax rule
3. Search tax rule using both Name and Tax Rate fields
   eg. Name = Alabama & Tax Rate = US-AL

Expected result (*)

1. Combined search executed and output is displayed to admin
2. Admin can continue using tax rate search again

Actual result (*)

1. MySQL error is thrown

Exception #0 (Zend_Db_Statement_Exception): SQLSTATE[23000]: Integrity constraint violation: 1052 Column 'code' in where clause is ambiguous, query was: SELECT COUNT(DISTINCT main_table.tax_calculation_rule_id) FROM tax_calculation_rule AS main_table
LEFT JOIN tax_calculation AS tc ON main_table.tax_calculation_rule_id = tc.tax_calculation_rule_id
LEFT JOIN tax_calculation_rate AS rc ON tc.tax_calculation_rate_id = rc.tax_calculation_rate_id WHERE ((code LIKE '%Alabama%')) AND ((rc.code LIKE '%US-AL%'))

2. In production mode blank area displayed instead of grid, admin can not use tax rate search anymore until session/cookies cleared manually
   

[magento-engcom-team]

Hi @robyerevan. 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-engcom-team give me 2.3-develop instance - upcoming 2.3.x release

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

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

• yes
• no

[robyerevan]

@magento-engcom-team give me 2.3-develop instance

[magento-engcom-team]

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

[magento-engcom-team]

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

[robyerevan]

Reproduced on
Magento 2.3-develop instance

[magento-engcom-team]

Hi @krishprakash. 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-engcom-team 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. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• Next steps are available in case you are a member of Community Maintainers.

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

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

[krishprakash]

@magento-engcom-team give me 2.3-develop instance

[magento-engcom-team]

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

[magento-engcom-team]

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

[magento-engcom-team]

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

[amol2jcommerce]

• @magento-engcom-team give me 2.3-develop instance

[magento-engcom-team]

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

[magento-engcom-team]

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

[magento-engcom-team]

Hi @shikhamis11. 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-engcom-team 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. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• Next steps are available in case you are a member of Community Maintainers.

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

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

[magento-engcom-team]

✅ Confirmed by @shikhamis11
Thank you for verifying the issue. Based on the provided information internal tickets MAGETWO-98517, MAGETWO-98518 were created

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

[magento-engcom-team]

Hi @robyerevan. Thank you for your report.
The issue has been fixed in #21701 by @tuyennn in 2.3-develop branch
Related commit(s):

• 924dca297c1ac696e1362ec2e76a23676d87efa0

The fix will be available with the upcoming 2.3.2 release.

[magento-engcom-team]

Hi @robyerevan. Thank you for your report.
The issue has been fixed in #21535 by @tuyennn in 2.2-develop branch
Related commit(s):

• d935998b6f70c9f5943b817511b0b8576366cb55
• fb2d35484179f95c908de86cb4ac17f5dca228ae

The fix will be available with the upcoming 2.2.9 release.