Sage X3

commercebuild's Sync Agent, which replicates data from the SQL Server used by Sage 300, relies on change tracking being enabled on the database, as well as on the tables. For more information about ch...

Note: credit card fee is not the same as pre-auth increase. Pre-auth increase is a buffer (or a floating amount) that is added to the pre-authorization on the card via the payment gateway settings whe...

When we interact with Sage X3, we do so through the web services. Therefore, when you see the error X3 server is not allowed to ask the web service server to open a window -- which we typically see wh...

If your webstore is unable to connect to the server (for example, you are seeing "No SSH Connection" errors) follow these steps to restart the service. Start or Restart Symphony Client Service with th...

Whenever you have pricing issues on your web store, it is always helpful to send us screenshots from X3's Price Search screen. In the video below, we'll show you how. Please note that your X3 may be o...

commercebuild has recently begun upgrading web stores from Sync 1 to Sync 2, which is our improved replication software that keeps your web store up-to-date with your ERP. In this article, we'll go ov...

If you receive the following error message while processing an order: <<*>>ERROR MESSAGES (response)|*|Customer: Failed to update Sage CRM with customer number 'WEB00XXXX', named 'Starbuck...

This error can be associated with a failed order. If the web store is successfully connecting to Sage, which you can test by going to ERP Integration > Test Connection in your Dashboard, you shoul...

This error usually indicates that the credentials for Sage 300 or Windows server are incorrect. Once the correct credentials are known, they will need to be updated in Symphony Client, XM Symphony Cli...

FAILED - ERROR MESSAGES|*|Date incorrect (check the validity of the delivery and shipping dates). indicates that the order was placed on a day that was not selected as Default workdays in Sage because...