FAQ

FAQ

99. FAQ


Incompatibility with Magento version 2.3.x

ERP is compatible with Magento version 2.3.0 since its version 1.3.4.

If you’ve got a lower version, please update it to the last one available.

Also, Magento released their own inventory management system through version 2.3.0.

This system called ‘MSI’ is not compatible with our ERP stock management system.

That means if you want to make ERP work on version 2.3.0, you will have to disable all modules part of the MSI system.

You can find a way to disable them all through CLI command lines in the Magento developer documentation, please check the following link : Disable Inventory Management

Some tabs disappeared in ERP products view and orders view

Note

This has been fixed in ERP, since version 1.4.2.

Due to a know bug of the new versions of Magento 2, some tabs added by ERP will not be visible anymore after a Magento upgrade.

The solution to solve it is the following :

  • Open the file : /vendor/magento/module-backend/Block/Widget/Tabs.php

  • Change the following line (should be around line 302, in function applyTabsCorrectOrder) :

    $positionFactor = 1;
    
  • By this one :

    $positionFactor += 1;
    

Check the installed version of ERP

If you want to check which ERP version is currently installed on your server, there is a simple way to do it :

  • Edit the file app/code/BoostMyShop/Erp/composer.json
  • Check line 5 : "version": XXX, where “XXX” will be the version currently installed.

Translate ERP modules

You can translate any Magento 2 module creating the appropriate CSV file, where all translations will be written.

By default, we provide French translations for each module of ERP.

Depending of the module, here are locations of CSV file containing translations :

  • Advanced Stock : app/code/BoostMyShop/AdvancedStock/i18n/
  • Availability Status : not translated yet
  • Erp : app/code/BoostMyShop/Erp/i18n/
  • Order Preparation : app/code/BoostMyShop/OrderPreparation/i18n/
  • Organizer : app/code/BoostMyShop/Organizer/i18n/
  • Supplier : app/code/BoostMyShop/Supplier/i18n/
  • Ultimate Report : not translated yet

You can add translations for your own language by adding a CSV file into app/code/BoostMyShop/MODULE_NAME/i18n/ folder, naming the file with the abraviation corresponding to your language (ex : for French language, files have to be named fr_FR.csv).

ERP Dashboard is empty

It can happen that when you go into menu Embedded ERP > Dashboard, the screen displayed contains empty dashboards, even if you should have data displayed in it.

In this case, if you open your internet browser console, you should see the following error displayed :


To correct it, you will need to disable the option “Minify Javascript files” which is not compatible with our ERP dashboards.

This option is available from Stores > Configuration > Advanced > Developer > JavaScript Settings > Minify JavaScript Files.

Magento setup:upgrade command doesn’t complete

During the update/installation of Embbeded ERP extension, it can happen that Magento setup:upgrade get stuck during the Supplier module update.

You can resolve this situation modifying this file : app/code/BoostMyShop/Supplier/Setup/UpgradeData.php

Then, comment this part of the code, located between line 88 and line 107 :

if (version_compare($context->getVersion(), '0.0.32') < 0)
{
    try
    {
        $this->_state->setAreaCode('adminhtml');
    }
    catch(\Exception $ex)
    {
        //nothing, just mean that area code is already set
    }

    //init default value for supply_discontinued
    $productIds = $this->_productCollectionFactory->create()->getAllIds();
    $arrays = array_chunk($productIds, 200);
    foreach($arrays as $array)
    {
        $this->_productAction->updateAttributes($array, ['supply_discontinued' => 0], 0);
    }

}

This should resolve the issue and helps the setup:upgrade command to complete correctly.

Then, once the module has been correctly updated, installed, you’ll have to execute manually what this section of code was supposed to do.

To do it, go into grid ERP > Products.

Then, select all your products, and use massaction “Set product as not discontinued” :


Note

If you get a timeout error doing this, that means you are trying to update the discontinued attribute on too many products at the same time.

Simply select less products to process and try again.

Sales history are empty

Sales history are not refreshed automatically. They can be updated using an SSH command line :

php bin/magento bms_advancedstock:refresh_sales_history

You can add a cron task on this command line to get sales history updated at a defined interval.

Massactions 'Select all' and 'Unselect all' not working

Since Magento v2.4.0, some massaction available in ERP grids are not working correctly.
This is due to a Magento bug, here is the way to fix it :
1) Open the file :
app/code/Magento/Catalog/view/adminhtml/templates/product/grid/massaction_extended.phtml
2) Starting line 67, you should see :



3) Add a ";" after each "break" instruction to fix the bug. The code should now look like this :

    • Related Articles

    • FAQ

      5. FAQ
    • FAQ

      99. FAQ Flush Shipped Orders button doesn’t work? Only orders from the “In Progress” tab with a “shipped” preparation status are flushed using this button. At the end of the “Packing” step, you need to add a tracking number, or to click on the “Skip ...
    • FAQ

      6. FAQ What product types are supported? POS extension only supports simple products for the moment What payment methods are supported? POS supports only offline payment methods (any methods connecting to a server like credit card or Paypal are not ...
    • FAQ

      5. FAQ Error : A text must be provided to barcode before drawing This error means that our extension is not able to retrieve a barcode number for the current product, 2 possible reasons : You have not configured the barcode attribute in stores > ...
    • FAQ

      98. FAQ 1. Magento setup: upgrade command doesn’t complete During the update/installation of Embbeded ERP extension, it can happen that Magento setup:upgrade get stuck during the Supplier module update. You can resolve this situation modifying this ...