Skip to content

Requirements

Supported Environments

  • Shared cloud
  • Isolated cloud (lime-crm ^2.913.0)
  • On-premise with server v2024.3 or higher.

General Requirements

In order to use the ERP Connector, the following requirements must be satisified:

  • The YTD growth component in the table is only supported in v2022.2 or higher.
  • The Lime CRM API:s must be accessible from the server where the Syncify service will be installed. For cloud based ERP systems, that means it must be accessible from the internet.
  • Database names on fields on the company object follows the list on Technical. If not, then Syncify must change the migration scripts and integration field mappings.
  • If using in Lime CRM Desktop Client: Lime Bootstrap v1.12 or higher v1.x.

For All On-Premise ERP Systems (Even if Hosted Online)

This applies to Microsoft Dynamics NAV, Visma Business, Business Central, Visma Administration, Visma Nova, and Visma Global.

  • A server where the Syncify service can be installed (can be installed on the ERP server). The server must have the following:
    • The ERP system must be reachable from the server.
    • Administrative rights to the server during installation.
    • Powershell 3.0 installed.
    • Python 3.6 or higher installed.
    • .NET framework 4.7.2 or higher installed.

Specific Requirements

These are the additional, specific requirements per ERP system.

Björn Lundén Administration

  • A public key1.

Business Central

On-premise

Follow the requirements for NAV.

Cloud
  • Syncify will need the following information:
    • Tenant ID, Client ID, Client secret and RefreshToken.2
  • Following web services activated, with both ODATA and SOAP URLs made available:
    • Contact
    • Customer
    • SalesPeople

e-conomic

Exact Online

More information will come.

Fortnox

  • Fortnox with integration must be activated and the "Lime CRM" integration ordered1.

Maconomy

  • External API URL (iAccess) with Rest API v.2.
  • Username and password for an API user1.
  • The user needs to have access to all required cards, e.g. customer card, employees, invoices.

Microsoft Dynamics NAV

  • NAV 2009 R2 or higher is required.
  • A user in Microsoft Dynamics NAV with access to the web service.
  • The following pages need to be published in the webservice (and available externally during installation):
    • CustomerCard
    • CustomerLedgerEntries
    • DetailedCustomerLedgerEntries
    • Items
    • PostedSalesCreditMemo
    • PostedSalesInvoice
    • CountriesRegions
    • GeneralLedgerSetup
    • SalesPeoplePurchasers
  • An internal URL to the web service. This will be used when the integration is running.
  • An external URL to the web service. This will only be used during installation. The reason is that the web service must be accessed from Syncify's development environment. This can also be achieved with a VPN connection, in which case one must be provided.

Monitor G5

Power Office Go

  • Client Id.

Tripletex

  • An employee token1.

Uniconta

  • LoginId and Password for a user that is a server user.
  • The user needs to have access to customers/invoices/invoice rows/VAT codes/employees. This is most likely requiring full access in the system. Access is specified when setting up the user.
  • A default customer group should be specified in settings. Otherwise the system takes the first one that's found when creating a new customer.

Visma Administration

  • Visma Administration with integration must be activated.
  • A number series must be active so that new customers automatically will get a unique customer number.
  • A username and password for the integration to use1.

Visma Business

  • One of the following:
  • A user (does not have to be an administrator) with module Named User with username and password to Visma Business1.
  • A user with the module Server integration plus a normal user to use as a context user.
  • Web service for Visma Business (VBS)1.

Visma eEkonomi

More information will come.

Visma Global

  • BAPI key (Must be 17 characters long).
  • VAF (Visma Application Framework).
  • Database username and password1.
  • Syncify service user needs to be an approved user in Visma Global. Under "Administrator rutiner", "Adgangsgruppeoppsett".

Visma.Net

  • A dedicated integration user1. The user must have the roles Financial User and Financial Administrator.

Visma Nova

  • Public URL to the webservice.
  • Hash key for login1.

  1. May result in an additional fee from the supplier. ↩↩↩↩↩↩↩↩↩↩↩

  2. A guide on how to retrieve these will be provided by Syncify during the implementation project. ↩