How to Fix the "Syntax error or access violation: 1072 Key column 'customer_group_id' doesn't exist in table" issue?
How to Fix the "Syntax error or access violation: 1072 Key column 'customer_group_id' doesn't exist in table" issue?
The outlined error is related to the amasty_groupcat_rule_product table, which is used by the Customer Group Catalog extension and serves as an index table. Data gets written into it only after performing a full Magento reindex. However, some issues may occur when the structure of this table is corrupted or doesn’t match the extension’s expectations, for example, if the customer_group_id column is missing.
To fix the error, follow these steps:
Step 1. Create DB backups;
Step 2. Run the following SQL query:
DROP TABLE amasty_groupcat_rule_product
Step 3. Execute these commands, from your Magento root folder via CLI:
The actual configuration and rules are stored in the amasty_groupcat_ruletable, so you will not lose them. And theamasty_groupcat_rule_product table will automatically be recreated with the proper structure during setup:upgrade.
Should you have any questions or require assistance, reach out to our support team - we're happy to help.
After upgrading Magento to version 2.4.5 you can see the error: TypeError: Magento\Elasticsearch\Model\ResourceModel\Fulltext\Collection\SearchResultApplier::categoryProductByCustomSortOrder(): Argument #1 ($categoryId) must be of type int, array ...
Kindly note that the API functionality for Customer Group Catalog is available as a part of an active product subscription or support subscription. GET /V1/amasty_groupcat/rule/:ruleId - to retrieve information about a specific customer group catalog ...
Out-of-the-box, the Customer Group Catalog module allows enabling rules to cover out-of-stock products. To explicitly include out-of-stock items in your customer group catalog rules, use either of these options: Option 1: Use the Apply to Out of ...
This error occurs when the inventory module is enabled, yet the inventory is not used. The issue can be resolved by adjusting the InventoryResolver.php file that is located either in the app/code/Amasty/Feed/Model/ or vendor/amasty/feed/Model/ ...
You might come across the following error in system logs when Live Search is used. The "elasticsearch" part can also be slightly different in various cases, for example, "elasticsearch7" or "opensearch" can be mentioned instead: report.ERROR: ...
At Amasty, we understand that some of our clients require customized features to perfectly align the extension with their business needs. If you have developed new functionality within an Amasty module and would like to share it, please submit a ticket