Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
moneyworks:magento_integration [2015/07/22 13:24] – Adrian Boone | moneyworks:magento_integration [2024/03/20 15:20] (current) – Fix broken link for component and typo Adrian Boone | ||
---|---|---|---|
Line 13: | Line 13: | ||
=====Introduction===== | =====Introduction===== | ||
- | This is a standalone application (Windows or Mac) using our [[: | + | This is a standalone application (Windows or Mac) using our [[:moneyworks: |
We call this process ' | We call this process ' | ||
+ | {{ : | ||
- | + | There are also some customised versions of the Connector which connect to MySQL databases, either directly or via an API. It can also be customised to support other ecommerce platforms e.g. Prestashop. Please contact us for more details if you're interested. | |
- | + | ||
- | + | ||
- | {{ : | + | |
=====Entering the customisation code===== | =====Entering the customisation code===== | ||
Line 27: | Line 25: | ||
Available from the //Sync -> Customisation code// menu item. This code determines which options are available and must be entered first to enable the other menu items. | Available from the //Sync -> Customisation code// menu item. This code determines which options are available and must be entered first to enable the other menu items. | ||
- | By default, the connector | + | By default, the Connector |
=====Setting up the sync parameters===== | =====Setting up the sync parameters===== | ||
- | Available from the //Sync -> Setup// menu item. This consists of four tabs with settings for the Moneyworks connection and Magento connection parameters, and also some Moneyworks-specific options and advanced options to control the sync process. | + | Available from the //Sync -> Setup// menu item. This consists of five tabs with settings for the Moneyworks connection and Magento connection parameters, and also some Moneyworks-specific options and advanced options to control the sync process. |
====Moneyworks connection==== | ====Moneyworks connection==== | ||
- | This tab controls how the Moneyworks | + | This tab controls how the Connector connects to Moneyworks: |
- | {{ : | + | {{ : |
+ | It allows you to enter the parameters for the Moneyworks connection: | ||
- | The left hand side of the tab allows you to enter the parameters for the Moneyworks connection: | + | |
- | + | ||
- | | + | |
* The datafile location or filename must be entered (full path must be entered if a local file). | * The datafile location or filename must be entered (full path must be entered if a local file). | ||
- | * The location of the Moneyworks executable must be entered. | + | * The location of the Moneyworks executable must be entered, unless the connection is via REST. |
* Enter the document user name and password (even if blank) in all cases. | * Enter the document user name and password (even if blank) in all cases. | ||
* The Gold client license key is only needed if connecting to a Gold server. | * The Gold client license key is only needed if connecting to a Gold server. | ||
* The server IP address and port number are not needed for connecting to a local file. | * The server IP address and port number are not needed for connecting to a local file. | ||
- | * The DC user name and password should be entered (even if blank) if connecting to a Datacentre server, | + | * The DC user name and password should be entered (even if blank) if connecting to a Datacentre or Datacentre REST server. If it's a Datacentre REST server connection, you can specify if the connection is secure or not; if it's a regular |
- | The right hand side of the tab allows you to send commands to Moneyworks (see the Moneyworks manual for details), and you can use the examples in the //Input// drop-down menu to check that the connection is setup correctly e.g. selecting //evaluate expr=" | + | {{ : |
+ | |||
+ | By default, there is a single connection to the Magento database, but it is now possible for a single instance of the Connector to have multiple connections e.g. you may want to apply different rules and settings for different Magento stores and/or sync them to different Moneyworks data files. Apart from the synchronisation interval, all other settings can be different for each connection: | ||
+ | * Switch connection settings using the drop-down list at the top right. | ||
+ | * Add a new one (which will duplicate the existing connection settings) using the //+// button to the left of the drop-down list | ||
+ | * Remove the last one using the //-// button to the right of the drop-down list - obviously, you can't delete Connection1! | ||
+ | |||
+ | ====Moneyworks test==== | ||
+ | |||
+ | The second | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | For REST connections, | ||
+ | |||
+ | {{ : | ||
====Magento connection==== | ====Magento connection==== | ||
- | This tab controls how the Moneyworks | + | This tab controls how the Connector connects to Magento: |
- | {{ : | + | {{ : |
* Enter user name and password (API key) as supplied by the Magento site administrator. | * Enter user name and password (API key) as supplied by the Magento site administrator. | ||
Line 63: | Line 75: | ||
Click on the //Test// button to verify the connection. Clicking on //OK// will save the current connection settings, and //Cancel// will discard any changes made. | Click on the //Test// button to verify the connection. Clicking on //OK// will save the current connection settings, and //Cancel// will discard any changes made. | ||
+ | |||
+ | If you have multiple connections, | ||
====Moneyworks settings==== | ====Moneyworks settings==== | ||
Line 68: | Line 82: | ||
This tab allows you to customise how imported records appear in Moneyworks. When it is selected, the system attempts to read tax codes and shipping codes from the Moneyworks data file: | This tab allows you to customise how imported records appear in Moneyworks. When it is selected, the system attempts to read tax codes and shipping codes from the Moneyworks data file: | ||
- | {{ : | + | {{ : |
* //Highlight colour// controls how the imported records are coloured in Moneyworks. | * //Highlight colour// controls how the imported records are coloured in Moneyworks. | ||
* //Base currency code// should correspond to the base currency in the Moneyworks data file. | * //Base currency code// should correspond to the base currency in the Moneyworks data file. | ||
* The default and shipping tax codes are applied to orders which have a non-zero tax amount in Magento, otherwise the tax code is set to blank. | * The default and shipping tax codes are applied to orders which have a non-zero tax amount in Magento, otherwise the tax code is set to blank. | ||
- | * If //Use Moneyworks address for business | + | |
- | * If required, you can define a mask for the order/ | + | |
+ | * If required, you can define a mask for the order/ | ||
+ | * If left blank, Moneyworks will use the ID assigned by Magento. | ||
+ | * Depending on the customisation code entered, the same facility is available for assigning new customer codes. | ||
+ | * Note that there is a limit of 11 characters in Moneyworks for transaction and customer codes, so this determines the maximum length of the mask. | ||
+ | * Note that the numeric part of the Magento ID must not be longer than the number of trailing zeroes in the mask, otherwise it won't fit into the space available. If it doesn' | ||
* If set, the //Shipping code// is applied to all orders which have a non-zero shipping amount in Magento. This will normally be shown as an extra line in the invoice. | * If set, the //Shipping code// is applied to all orders which have a non-zero shipping amount in Magento. This will normally be shown as an extra line in the invoice. | ||
- | Note that most of these settings can be overridden by using a customised Moneyworks import map e.g. it may be necessary to have different tax codes for different transaction currencies, different types of product or different shipping destinations. In this case, the tax codes should be left blank here, and the connector | + | Note that most of these settings can be overridden by using a customised Moneyworks import map e.g. it may be necessary to have different tax codes for different transaction currencies, different types of product or different shipping destinations. In this case, the tax codes should be left blank here, and the Connector |
====Other settings==== | ====Other settings==== | ||
Line 83: | Line 102: | ||
This tab controls the sync process itself: | This tab controls the sync process itself: | ||
- | {{ : | + | {{ : |
* The Magento and Moneyworks sync timestamp fields control which records are imported into Moneyworks (and can be manually edited if needed e.g. to ignore failed records before a certain date): | * The Magento and Moneyworks sync timestamp fields control which records are imported into Moneyworks (and can be manually edited if needed e.g. to ignore failed records before a certain date): | ||
- | * Both refer to the local time on the Magento and Moneyworks server respectively (they can be in different time zones). | + | * Both refer to the local time on the Magento and Moneyworks server respectively (they can be in different time zones). By default, Magento runs on the UTC time zone. |
* When a sync process has completed without errors, both timestamps are updated so that the records are not re-imported the next time (records imported into Moneyworks store the corresponding Magento timestamp in one of the user/custom fields). | * When a sync process has completed without errors, both timestamps are updated so that the records are not re-imported the next time (records imported into Moneyworks store the corresponding Magento timestamp in one of the user/custom fields). | ||
* If there is an error, then the sync timestamps are not updated, and the next sync will retry to import the failed record(s), and skip any which have previously been imported successfully. | * If there is an error, then the sync timestamps are not updated, and the next sync will retry to import the failed record(s), and skip any which have previously been imported successfully. | ||
- | * If the //Sync interval// is set to any value other than zero, the connector | + | * If the //Sync interval// is set to any value other than zero, the Connector |
* If //Generate CSV import files// is checked, the connector won't delete the temporary CSV import files that it generates (in the // | * If //Generate CSV import files// is checked, the connector won't delete the temporary CSV import files that it generates (in the // | ||
* In some circumstances, | * In some circumstances, | ||
+ | * If // | ||
+ | * If an email address has been entered in //Email address for notifications//, | ||
+ | * If no email address has been entered, or the // | ||
+ | * Note that there is a throttle in place to prevent another error email being sent less than an hour since the previous one unless it also contains a warning. | ||
===== Initial setup of Moneyworks datafile ===== | ===== Initial setup of Moneyworks datafile ===== | ||
Line 101: | Line 124: | ||
* Make sure that the base currency in Moneyworks has been set correctly. | * Make sure that the base currency in Moneyworks has been set correctly. | ||
* Make sure that the tax codes in Moneyworks have been setup correctly, with the same rates as in Magento. | * Make sure that the tax codes in Moneyworks have been setup correctly, with the same rates as in Magento. | ||
+ | |||
+ | ===== Upgrading the Connector ===== | ||
+ | |||
+ | - Make sure that the Connector is not currently syncing (or about to sync) with Magento. One way to check this is to look at the timestamp of the latest log file (in the //Logs// folder) and compare that with the next scheduled time. | ||
+ | - Exit the Connector | ||
+ | - Make a backup copy of the // | ||
+ | - Copy over the updated application files as directed (usually only // | ||
+ | - If an import map has been updated, then copy it to the // | ||
+ | - Restart the Connector - if prompted for a data file, browse to the *.4DD Connector data file (usually // | ||
+ | - Check the Connector settings and set appropriate values for any which have been newly added since the previous version | ||
+ | |||
+ | It is possible to run multiple Connector instances on the same machine as long as: | ||
+ | * They are installed in different folders | ||
+ | * They connect to different Moneyworks data files | ||
+ | * They don't try to sync at the same time - either set their scheduling to be different, use a REST connection for at least one of them, or install multiple instances of the Moneyworks client | ||
===== Common errors ===== | ===== Common errors ===== | ||
Line 108: | Line 146: | ||
* Mismatch between the item codes in Moneyworks and those in Magento | * Mismatch between the item codes in Moneyworks and those in Magento | ||
- | When an import fails, then the next sync will restart from the same point as the previous one, so any records deleted in Moneyworks may magically be resurrected! If the import error cannot be fixed, then it can be ignored by manually setting the timestamps | + | When an import fails, then the next sync will restart from the same point as the previous one, so any records deleted in Moneyworks may magically be resurrected! |
+ | * This will likely generate informational messages in the log file for any records which were successfuly imported the last time. | ||
+ | * Regardless of the sync interval setting on the //Other Settings// tab, there will not be more than one error email per hour, unless the log file also contains a warning. | ||
+ | * If the import error cannot be fixed, then it can be ignored by manually setting the Magento timestamp | ||
==== Troubleshooting ==== | ==== Troubleshooting ==== | ||
- | - Check log file created for each sync in the // | + | - Check the log file created for each sync in the // |
- | - Switch on //Generate CSV import files// on the //Other Settings// tab - this creates CSV files in the // | + | - Switch on //Generate CSV import files// on the //Other Settings// tab. This creates CSV files in the // |
- | - If connecting to Magento, enable | + | - Enable |
+ | - If the Connector is configured to use a REST connection, enabling XML debugging will also create XML import files in the // | ||
+ | - These XML files can then be manually imported into Moneyworks, either directly in Moneyworks or by making use of the //Execute// button on the // | ||
===== Appendix: Magento API fields used by Connector ===== | ===== Appendix: Magento API fields used by Connector ===== |