LoriaLINK Administrator Guide

LoriaLINK is supplied with a default integration profile that is set up to map the most common data betweenSage CRM and Sage 50 as a two-way synchronsiation. This includes settings that instruct LoriaLINK how to deal with any duplicate records that it encounters.

Please review these notes before running LoriaLINK for the first time to ensure that these settings meet your requirements. It is easy to adapt the default settings by adding or removing mappings and changing other settings as relevant.

LoriaLINK can either be run manually, as required, or set up to run on a regular schedule that meets the needs of the business. This ensures that the data is kept up to date between the systems whilst allowing for administrative tasks to be performed as necessary and to run larger processes, (such as updating price lists and product information), out of office hours.

This article explains how to set up LoriaLINK to synchronise automatically in the background so taht users have access to the latest information when they need it.

LoriaLINK has been developed to be configured easily to meet most real-world business applications. In addition to Sage 50, LoriaLINK can integrate with many other Sage and third-party applications. Any CRM entity can be synchronised with Sage 50 making it suitable for retail and commercial applications as well as other business applications where one or more simultaneous connections is required. Mappings can also be created for custom fields to synchronise custom data between Sage CRM and other applications.

This article overviews the main LoriaLINK settings. More detailed information is available in the articles in that Administrator Guide relating to the specific area.

In order to install LoriaLINK, you will need to know the login credentials with administrator rights for the nominated Sage CRM user account and for the other application(s) that are to be synchronised.

This article steps through the set-up stages required to integrate Sage CRM with Sage 50 but can be applied generally to any other integration.

LoriaLINK offers a significant amount of control over the way that the data synchronisation is handled between Sage CRM and the other application(s). In addition to straight-forward field mappings that control which data is transferred, it is possible to control the frequency of synchronisation on a field by field basis and whether data is one- or two-way. This ensures that the most dynamic data can be synchronised most frequently, keeping the information available to users up to date but limiting the server load. It is also possible to program additional commands that carry out special processes on selected data during the integration process if required.

This article explains how to review and amend the integration settings in LoriaLINK.

Core Sage CRM entities include companies, people, opportunities, quotes and orders all of which can be synchronised to a third party application using LoriaLINK. However, the development of Sage CRM often includes the addition of custom entities to meet specific client requirements. This can include a wide range of applications such as managing training programmes, arranging and running events, job and project management and tracking information about machinery or other assets. LoriaLINK can easily be configured to include data from these custom entities so that costs and revenue can be tracked to show income and profit for the specifc entity and not just against the client company.

This article explains how to set-up and maintain settings for standard and custom entities.

LoriaLINK can be configured to synchronise any entity field in Sage CRM with another database application. Controls can be set to determine the frequency of synchronisation and also whether the transfer is one- or two-way.Additional commands can be programmed to carry out any special additional programming that might be required.

This article explains how to set up and maintain ssettings for individual field mappings and set the required synchronisation frequency

On occasions it may be necessary to run a one-off synchronisation on some or all of the data, This could occur after a data import or if any maintenance work such as data cleaning has been carried out on one or other of the integrated systems.

This article explains how to set up and run a synchronisation with LoriaLINK outside of the normal schedule.

In order to ensure efficient running of LoriaLINK and also to provide access to operational information for troubleshooting and support, logs are maintained for each synchronisation. Logging can be set at different levels appropriate to the needs of the business and can be set to auto-clear historic log files in order to reduce storage requirements.

This article explains how to configure and maintain logging levels.