Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
addons:erpconnector:installation [2018-12-02 22:09] 127.0.0.1 external edit |
— (current) | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ===== Lime CRM Layout ===== | ||
| - | These tables and fields must be created before you can use the ERP Connector. The fields will be created by LIP. However, if the Lime CRM application already is in the Cloud environment, | ||
| - | ==== Company ==== | ||
| - | On the company card, some fields are mandatory and some are not. Please note that either way, database field names are hardcoded in the javascript code in the LBS app as well as in Syncify' | ||
| - | |||
| - | The following company fields are used: | ||
| - | |||
| - | **Table name:** '' | ||
| - | |||
| - | ^ Field Name ^ Field Type ^ Field Label ^ Required | ||
| - | | name | Text field | Name | True | 200 | No | The name of the company | | ||
| - | | erpid | Text field | key | False | 16 | Yes | The integration key, Set label key to avoid duplicates | | ||
| - | | erp_turnover_yearnow | Decimal | N/A | False | N/A | Yes | Populated by the integration | | ||
| - | | erp_turnover_lastyear | Decimal | N/A | False | N/A | Yes | Populated by the integration | | ||
| - | | erpconnector_graph | HTML (tab) | N/A | N/A| N/A | Yes | HTML tab for showing the graph for paid invoices the last 5 years | | ||
| - | | invoice| Relation (tab)| N/A | N/A| N/A | Yes | Populated by the integration | | ||
| - | |||
| - | ==== Invoice==== | ||
| - | Invoices are connected to the company using " | ||
| - | |||
| - | **Table name:** '' | ||
| - | |||
| - | ^ Field name ^ Field Type ^ Field label ^ Required ^ Length ^ Description ^ | ||
| - | | invoice_number| Text field | N/A | False | 64 |Unique invoice number | | ||
| - | | company | Relation (field) | N/A | False | 256 | Relation to company | | ||
| - | | customerid | Text field| N/A | False | 128 | Customer ID for matching to company | | ||
| - | | customer_reference | Text field | N/A | False | N/A | Customer reference from ERP| | ||
| - | | coworker | Relation (field) | N/A | False | N/A | Company reference (Our reference) | | ||
| - | | invoice_type | Text field | N/A | False | 64 | Invoice type | | ||
| - | | invoice_date| Time (date) | N/A | False | N/A | When invoice is booked | | ||
| - | | invoice_expires| Time (date) | N/A | False | N/A | When invoice expires | | ||
| - | | invoice_sum| Decimal | N/A | False | N/A | Sum ex VAT (moms) | | ||
| - | | invoice_vat| Decimal | N/A | False | N/A | VAT (moms) | | ||
| - | | invoice_total_sum | Decimal | N/A | False | N/A | Sum incl VAT| | ||
| - | | currency | Text field | N/A | False | 32 | Currency | | ||
| - | | invoice_balance | Decimal | N/A | False | N/A | Invoice balance (saldo)| | ||
| - | | paid| Yes/no | N/A | False | N/A | Yes if it is paid| | ||
| - | | paid_date | Time (date) | N/A | False | N/A | The date when payment is registered | | ||
| - | | invoice shredded | Yes/no | N/A | False | N/A | Yes if the payment is shredded (makulerad) | | ||
| - | |||
| - | ==== Invoice Row==== | ||
| - | Invoice rows are connected to an invoice using the invoice number. The complete invoice row table is part of the LIP Package. | ||
| - | |||
| - | **Table name:** '' | ||
| - | |||
| - | ^ Field name ^ Field Type ^ Field label ^ Required ^ Length ^ Description ^ | ||
| - | | invoice | Relation (field) | N/A | Yes | N/A | Relation to invoice | | ||
| - | | item | Text field | N/A | Yes | 128 | Item | | ||
| - | | description| Text field| N/A | Yes | 128 | Description of Items | | ||
| - | | units | Decimal | N/A | Yes | N/A | Number of items | | ||
| - | | row_margin| Decimal | N/A | Yes | N/A | Contribution margin | | ||
| - | | row_value| Decimal | N/A | Yes | N/A | Sum of row | | ||
| - | | rowid | Text field | N/A | Yes | 32 | Used to make a row unique (hidden) | ||
| - | |||
| - | ===== Lime Bootstrap App ===== | ||
| - | The Lime Bootstrap app both concludes the buttons for sending a new or updated customer to the ERP system as well as the invoice overview graph shown in the HTML tab on the company card. It is part of the LIP package. | ||
| - | |||
| - | It is possible to increase the logging to the Lime CRM info log tab when making calls to the Syncify services. Do this by adding the config parameter '' | ||
| - | |||
| - | <code javascript> | ||
| - | ' | ||
| - | </ | ||
| - | |||
| - | |||
| - | ===== LIP Package ===== | ||
| - | Download the LIP zip file for the latest release from [[https:// | ||
| - | |||
| - | ===== Syncify Service ===== | ||
| - | Syncify has built two different services. One for cloud based ERP systems (Fortnox, e-conomic and Visma.Net) and one for on-premise ERP Systems (Visma Administration, | ||
| - | |||
| - | If the ERP system is installed on-premise, the Syncify service must be installed and configured on the ERP system server. Syncify is responsible for the all installations of their service. | ||
| - | |||
| - | If the ERP system is cloud based there is no need for a local Syncify service. The integration is instead registered in Syncify' | ||