Connect SoftOne or Entersoft
For administrators: connect your SoftOne Soft1 or Entersoft Business Suite ERP (ENTERSOFTONE) to Filodos. The connection reads your customer and depot sites, and it can write visit notes back into the ERP. Part of the documentation.
What the connection does
- Sites into zones. Filodos reads the customer, branch, or depot list of the ERP. Each site with coordinates becomes a zone on the fleet map. See ERP sites and zones.
- Visit notes into the ERP. When a vehicle leaves an ERP zone, Filodos can write one note into the ERP: which vehicle, which site, the arrival and departure times. See Visit notes in the ERP.
Filodos reads the ERP every 6 hours. A manager or an administrator can also start a sync at once. A sync never deletes a zone.
Who can do what
Administrators own the connection: the login to your ERP. Managers run the work on top of it.
| Action | Admin | Manager | Driver |
|---|---|---|---|
| Add or delete a connection | Yes | No | No |
| Change the connection properties: name, API address, integration user, passwords, login fields, pause and resume | Yes | Read only | No |
| Change the workflow: site source, columns, zones, visit notes | Yes | Yes | No |
| Test the login, sync the sites, set a site location, read the visit notes | Yes | Yes | No |
What you need
Get these values from your ERP partner before you start.
- The product: SoftOne (Soft1, also oncloud) or Entersoft Business Suite.
- The API address. SoftOne:
https://<serial>.oncloud.gr/s1services. Entersoft: the address of the Entersoft Web API server, for examplehttps://erp.example.gr/eswebapi. - An integration user and its password. The user needs read access to customers. For visit notes, it also needs write access to the note object.
- SoftOne: the Web Account
appId. Optional: the company, branch, module, and reference id (REFID) of the login. Empty values select the first choice of the login. - Entersoft: the branch id (
BranchID) and the language (usuallyel-GR). The subscription id and password only if your installation uses them.
Do not use an administrator account of the ERP. Make a separate integration user with the smallest access that works. Then you can stop the connection at any time from the ERP side.
Add a connection
- Sign in as an administrator. Open Organization → ERP.
- In New connection, select the ERP: SoftOne (Soft1) or Entersoft Business Suite.
- Type a name, the API address, the integration user, and the password.
- Type the login fields of your ERP (see What you need).
- Click Add connection.
- Click Test login. The answer shows the company and branch (SoftOne) or the user (Entersoft) that Filodos logged in as.
- Continue with the workflow: ERP sites and zones.
Filodos stores the passwords encrypted. The dashboard and the API never show a stored password again.
The API address must start with https://. Filodos connects from its server on the internet, so the address must be reachable from the internet.
Change, pause, or delete
- Change. Edit the fields in the Connection panel and click Save connection. Leave a password field empty to keep the stored password.
- Pause. Click Pause. No sync runs, and no visit note goes to the ERP. Queued notes wait. Click Resume to continue.
- Delete. Click Delete, then Confirm delete. Filodos removes the connection, its site list, and its queued notes. The zones stay on the map. Remove them on the Geofences page if you do not need them.
Troubleshooting
| Message | Cause and fix |
|---|---|
SoftOne login failed with a Greek message | The ERP refused the user, the password, or the appId. Check them with your partner. |
SoftOne login has no choice matching | The company or branch does not exist for this user. Clear the fields to use the first choice, or type the correct values. |
Entersoft login failed (HTTP 401) | The ERP refused the user, the password, the branch, or the subscription. The text after the colon is the message of Entersoft. |
unreachable | Filodos cannot reach the API address. Check the address and the firewall of the ERP server. |
HTTP 503 or another 5xx | The ERP server has a problem. The next sync tries again. |