Besides all specific pieces of configuration which are described in the previous topics, there is a general setup page for all other/general configuration settings.
The setup page
Go to Administration Setup to open this page. Here you can see which version of the software you are currently running and whether all connections are online.
If you ever need to change the credentials for the Data Hub, you can do that here. Be aware, this is rarely the case.
If you have moved your Magento to another URL, or if for some reason you want to use a new Access Token, you can update your settings here.
If you want to define pricing (the default prices for the public view / non-logged in customers) by using a dummy/template customer. You can fill in the Customer No you want to use here. Once this is done, you can setup sales prices & discounts for this customer, and the resulting prices will be what is shown on the web. You can override this setting on a website level.
If you set a customer number, then you should also specify a sales quote number series (Calculation Order Nos.). The system will use it to create temporary quotes to calculate prices. Do worry, this is temporary data, you won’t see theses quotes in the sales quote list within Business Central.
Order Processed Status – This is the order status why Business Central applies to your Magento orders, in order to make sure that Magento knows that Business Central is now handling this order. The default value is ‘erp_processing’. Be aware that this new status still has to be created in Magento as well. See the following page for more information: https://docs.magento.com/m2/ee/user_guide/sales/order-status-custom.html
Here is a list of all number series which Commerce 365 will use for its own entities. Most of these you probably just want to leave as they are. But the Customer Nos setting has a few possibilities. You can either select your standard customer number series. In this case, all new customers will just get a new number from the that standard number series. But, you could also decide to create a new number series specifically for ‘web customers’.
Commerce 365 comes with a logging mechanism. Specifically, during the implementation phase, or if you are researching a synchronization issue, it might be helpful to enable this. Depending on the Level you select, you’ll be presented just a list of errors or with much more information about what is happening within the synchronization module. If you set Level to Debug the system will generate a log that contains every request and you can exactly see the contents of each data object which is sent from or to Magento.
Commerce 365 makes use of Microsoft Azure Application Insights. You can enable it without entering a custom key. In this case, the system will send its information to our central application monitoring instance. But, you can also add your own key, and then all information is sent to your own Azure Monitoring instance.