Magento2: Admin -> Configuration -> Sales -> Tax browsers get frozen

[onlinebizsoft]

Preconditions (*)

Magento 2.3.3 (at least I'm getting the problem with multiple instances 2.3.3, tested with both Firefox 70.0.1 (64-bit))

Steps to reproduce (*)

1. Simply go to admin and open Configuration -> Sales -> Tax.
2. Wait for some seconds, page seems to be finish
3. After a while, you get browser warning which pages slow down the browser and users can't interact with any input
   (Varnish is disabled)

Expected result (*)

Page should work normally

Actual result (*)

Message appears (See screenshot)

[m2-assistant[bot]]

Hi @onlinebizsoft. 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.

@onlinebizsoft 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.

[m2-assistant[bot]]

Hi @itsPranith. 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: :point_down:

• [ ] 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.

[itsPranith]

@magento give me 2.3-develop instance

[magento-engcom-team]

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

[magento-engcom-team]

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

[bradleybrecher]

I am also experiencing this issue on 2.3.3. This is the 3rd issue I have seen with the tax module.

https://github.com/magento/magento2/issues/25020
https://github.com/magento/magento2/issues/25403

Any update on a fix?

[onlinebizsoft]

@magento give me 2.3-develop instance

[magento-engcom-team]

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

[magento-engcom-team]

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

[onlinebizsoft]

Vertex seems to be not showing in configuration in latest 2.3-develop. Anyone has any idea?

[navarr]

Vertex is a bundled extension that is not part of this repository, and so is not in the 2.3-develop branch.

If you are not using Vertex for tax calculation, I recommend disabling the module for a performance improvement on this screen. The slowness is caused by a UIComponent heavy user interface for selecting flexible fields.

It is unlikely we'll have a solution in the near future for the performance issues a subset of merchants are experiencing. Again, my recommendation in this scenario is to disable the vertex module if you are not using it (bin/magento module:disable Vertex_Tax)

[m2-assistant[bot]]

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: :point_down:

• [ ] 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.

[m2-assistant[bot]]

Hi @sdzhepa. 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: :point_down:

• [ ] 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.

[navarr]

Please find a patch addressing this issue here: https://gist.github.com/navarr/2ec2f22f71a769d8438fb237f58eabd4

[navarr]

This issue has been fixed as of Vertex 3.3.0 and will be included with Magento 2.3.4

[amitbdigitalaptech]

@navarr

If we upgrade Vertex to version 3.3.0 for Magento Open source 2.3.3 Then the issue will resolve or not?

[navarr]

@amitbdigitalaptech The issue should resolve, yes.

[amitbdigitalaptech]

@navarr
I don't think, it will work

I have tried by adding "vertex/module-tax": "3.3.0", at composer.json.

Getting below Error:

Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - magento/product-community-edition 2.3.3 requires vertex/product-magento-module 3.2.0 -> satisfiable by vertex/product-magento-module[3.2.0].
    - magento/product-community-edition 2.3.3 requires vertex/product-magento-module 3.2.0 -> satisfiable by vertex/product-magento-module[3.2.0].
    - vertex/product-magento-module 3.2.0 requires vertex/module-tax 3.2.0 -> satisfiable by vertex/module-tax[3.2.0] but these conflict with your requirements or minimum-stability.
    - vertex/product-magento-module 3.2.0 requires vertex/module-tax 3.2.0 -> satisfiable by vertex/module-tax[3.2.0] but these conflict with your requirements or minimum-stability.
    - Installation request for magento/product-community-edition 2.3.3 -> satisfiable by magento/product-community-edition[2.3.3].

Also, tried with composer update vertex/module-tax:3.3.0, it does not working. package is not updating.

[navarr]

@amitbdigitalaptech You need to add a replace directive to your composer.json:

replace: {
    "vertex/product-magento-module": "*"
}

Then, if address validation is desired, you'll have to require that module separately (like tax)

[amitbdigitalaptech]

@navarr
Thanks for all help

Can you please tell me, VertexSMB_TaxCE is Magento 1 module for vertax (officially)?

And How can I avoid tax apply for Some specify customer group at current M2 vertex module?

[navarr]

@amitbdigitalaptech: Customers can have a tax class or a tax code on their account. Both of these are sent to Vertex and you would create a taxability rule in vertex to avoid tax.